-
Notifications
You must be signed in to change notification settings - Fork 3
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
Segfault #5
Comments
We are not including this in the next grcompiler release (v. 5.1). |
The linked Debian bug report is from 2013 and the attachment there that gives details of the bug is no longer available, so this will not be addressed. |
The bug details are still available and valid for grcompiler 5.2. |
To be more explicit: You run get() without checking for end of file first. |
This is a test case involving very atypical input which nonetheless should not cause a crash. We need to at least modify the code changed in the commit mentioned above which runs "get() without checking for end of file first". |
Passing this back. Just because I inserted \r handling doesn't mean I am in a position to fix this bug. It's not obvious to me from reading and will require someone with a test setup and debug to dig in and find where the EOF failure is coming in. get() does EOF checking itself, so there should be no need for eof checking (which is tricky what with macros and #includes) at that point. I can believe the crash but not the proposed diagnostic solution. |
Commit 4ccd16d introduced a bug that crashes gdlpp. Find the details at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715950
The text was updated successfully, but these errors were encountered: