-
Notifications
You must be signed in to change notification settings - Fork 86
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
Possible crash on invalid input #54
Comments
Hi @lexxmark If I understand correctly, you are reporting a crash with a pretty old version of Bison (2.5.*), is that right? It might well be true, but the current release is 3.7.3, and with that version:
Note that the test suite (including the examples) are run with address sanitizer enabled, so it is very unlikely that such a bug would remain unnoticed. And FWIW, none of 3.0.5, 3.1, 3.2.4, 3.3.2, 3.4.2, 3.5.4, 3.6.4, 3.7.2 crashed. Not even the old 2.7
Finally, the source code reads: /* Free bitset BSET. */
void
bitset_free (bitset bset)
{
if (bset)
{
BITSET_FREE_ (bset);
free (bset);
}
} so I really doubt there is a problem here. Are you really using something older? There is no support for old Bisons. The only supported version currently is 3.7.3. Cheers! |
Thank you for investigation,
No it's winflexbison version 2.5.23 that has flex 2.6.4 and bison 3.7.1 I apologize it seems I use some outdated version of the bitset.c source code:
I will update gnu lib source code from the latest bison release next time I will upgrade winflexbison and this issue in my project should vanish. Thank you again and sorry for bothering you, |
😄 No worries. Cheers! |
I'm porting GNU bison on windows and got an issue describing crash on some invalid input file.
lexxmark/winflexbison#64
I reproduced it and stack trace is following:
states_free ()
closure_free()
bitset_free (ruleset);
BITSET_FREE_ (bset); <<<< bset is NULL
Could you check if it also affect original bison code under linux?
The text was updated successfully, but these errors were encountered: