-
Notifications
You must be signed in to change notification settings - Fork 160
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 after quitting from a break loop #397
Comments
Simpler example. Also existed since at least 4.7.2 (earliest copy of GAP I have). Annoyingly nothing useful comes up from the debugger (which suggests misplaced longjump).
|
Turns out this is coming from a strange source:
This also crashes. If you put any extra character at the end of the string |
Yup, some how a read eval error long jump is causing us to segfault (not sure exactly why, or how), when we fall off the end of the string. |
Fix #397 (Segfault after quitting from a break loop)
It seems this is still not fixed. I am using latest release version (GAP 4.8.6, 12-Nov-2016, build of 2016-11-16 16:01:19). |
@wagh thanks for checking. The fix, committed in cf6272a by @ChrisJefferson, went to the master branch, so this will appear in GAP 4.9 release. I've just tried your example, and I can't reproduce the crash with the current master branch. |
@alex-konovalov thanks for the reply. I will check it after 4.9 release. As the commit was in April, and in the master branch, I thought it was already incorporated in the latest release. |
The following code leads to an error, as documented:
EvalString( "DeclareGlobalFunction( "a" );" );
However, exiting the break loop and executing it again leads to a different error, and exiting the 2nd break loop lead to a segmentation fault:
The text was updated successfully, but these errors were encountered: