Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing close brace causing segfault in >v3.8 parser code. #439

Open
wfpokorny opened this issue Oct 3, 2021 · 0 comments
Open

Missing close brace causing segfault in >v3.8 parser code. #439

wfpokorny opened this issue Oct 3, 2021 · 0 comments
Assignees
Labels
bug? reported as bug; triage pending

Comments

@wfpokorny
Copy link
Contributor

In releases / branches which include the newer parser updates (>3.8 release code), missing close brace(s) causing seg faults for both scale functions and vector functions where the function ID is called before the definition is finished. The function definition being unfinished because it's missing one or more closing braces.

v3.8 beta two and earlier releases correctly complain about the function being called before it's defined and suggesting a missing brace might be the cause.

See the attached tarball for two scenes and a README detailing the fixes I've made to my playpen branch.

v4_povr_parserSegFault_missingBrace_Oct01_2021.tar.gz

@wfpokorny wfpokorny added the bug? reported as bug; triage pending label Oct 3, 2021
@wfpokorny wfpokorny changed the title Missing close brace causing segfault in >v3.8 parser code [BUG] [Parser] Missing close brace causing segfault in >v3.8 parser code. Oct 3, 2021
@chris20 chris20 self-assigned this Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug? reported as bug; triage pending
Projects
None yet
Development

No branches or pull requests

2 participants