abrt 1.0.8 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/lib/gcl-2.6.8/unixport/saved_ansi_gcl -dir /usr/lib/gcl-2.6.8/unixport/ -libdir /usr/lib/gcl-2.6.8/ -eval '(setq si::*allow-gzipped-file* t)' -eval '(setq si::*tk-library* \"/usr/lib64/tk8.5\")' component: gcl executable: /usr/lib/gcl-2.6.8/unixport/saved_ansi_gcl kernel: 2.6.32.9-70.fc12.x86_64 package: gcl-2.6.8-0.7.20090701cvs.fc12 rating: 4 reason: Process /usr/lib/gcl-2.6.8/unixport/saved_ansi_gcl was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine)
Created attachment 400130 [details] File: backtrace
Is this crash reproducible? If so, can you tell me how to provoke it? Thanks.
(In reply to comment #2) > Is this crash reproducible? If so, can you tell me how to provoke it? Thanks. I don't know, I just tried to run gcl and it happened.
Does it happen every time you try to run gcl?
(In reply to comment #4) > Does it happen every time you try to run gcl? Yes. I get the following message: Segmentation fault (core dumped) Lisp worked fine on Fedora 11, I don't know what is wrong now.
It appears that you are running x86_64 F12. That's what I am running, too, but it doesn't crash for me. That implies some environmental difference between our setups that is provoking the crash for you. The backtrace shows that gcl is unable to mprotect() a range of memory. It then tries to throw an error, but it appears that the error throwing code isn't initialized, which leads to the crash. So we have to figure out why the mprotect() call is failing. Are you up for some debugging? If so, could you run with a breakpoint set on sgbc.c:1738? Each time the breakpoint is hit (which may be either once or twice, I'm not sure), find the values of the following variables: first_protectable_page type_map[0] sgc_type_map[0] Also, if you have customized any /proc or /sys settings that relate to memory, that is also useful information. Thanks!
gcl-2.6.8-0.7.20100201cvs.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/gcl-2.6.8-0.7.20100201cvs.fc13
gcl-2.6.8-0.7.20100201cvs.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/gcl-2.6.8-0.7.20100201cvs.fc12
Once one of those updates hits the updates repository, could you please try it out to see if it solves your problem? I still haven't been able to reproduce the problem, but this update contains a couple of potential fixes for it. Thanks.
gcl-2.6.8-0.7.20100201cvs.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update gcl'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gcl-2.6.8-0.7.20100201cvs.fc13
gcl-2.6.8-0.7.20100201cvs.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update gcl'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gcl-2.6.8-0.7.20100201cvs.fc12
gcl-2.6.8-0.7.20100201cvs.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
gcl-2.6.8-0.7.20100201cvs.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.