Version-Release number of selected component: gap-core-4.5.7-1.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/bin/gap -q -r -R crash_function: RNamName executable: /usr/bin/gap kernel: 3.8.2-206.fc18.x86_64 uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 RNamName at ../../src/records.c:98 #1 CallErrorInner at ../../src/gap.c:1436 #2 ErrorReturnVoid at ../../src/gap.c:1603 #3 EvalRefGVar at ../../src/vars.c:1051 #5 EvalUnknownBool at ../../src/exprs.c:198 #6 EvalNot at ../../src/exprs.c:327 #7 ExecIf at ../../src/stats.c:287 #8 ExecSeqStat at ../../src/stats.c:161 #9 DoExecFunc1args at ../../src/funcs.c:861 #10 CallErrorInner at ../../src/gap.c:1446
Created attachment 710678 [details] File: backtrace
Created attachment 710679 [details] File: build_ids
Created attachment 710680 [details] File: cgroup
Created attachment 710681 [details] File: core_backtrace
Created attachment 710682 [details] File: dso_list
Created attachment 710683 [details] File: environ
Created attachment 710684 [details] File: limits
Created attachment 710685 [details] File: maps
Created attachment 710686 [details] File: open_fds
Created attachment 710687 [details] File: proc_pid_status
Created attachment 710688 [details] File: var_log_messages
Thanks for the report. Is this crash repeatable?
From looking at the backtrace, it appears that gap was unable to take the negation of some variable it didn't know about, and from there got into an endless loop of trying to print an error message involving the variable, with each attempt triggering another error. My attempts at reproducing have so far been unfruitful. Even with fairly complex expressions, I get: Error, Variable: 'foo' must have a value If you can tell me how to reproduce this, it would be very helpful. Thanks.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.