Bug 735605 - [abrt] gcl-2.6.8-0.8.20110516cvs.fc14: error: Process /usr/lib/gcl-2.6.8/unixport/saved_ansi_gcl was killed by signal 6 (SIGABRT)
Summary: [abrt] gcl-2.6.8-0.8.20110516cvs.fc14: error: Process /usr/lib/gcl-2.6.8/unix...
Alias: None
Product: Fedora
Classification: Fedora
Component: gcl
Version: 14
Hardware: x86_64
OS: Unspecified
Target Milestone: ---
Assignee: Jerry James
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:fe8c727e0e559153c879cffdc7c...
Depends On:
TreeView+ depends on / blocked
Reported: 2011-09-04 00:01 UTC by Bruce-Robert Pocock
Modified: 2011-10-29 17:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-10-29 17:52:17 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (230.74 KB, text/plain)
2011-09-04 00:01 UTC, Bruce-Robert Pocock
no flags Details

Description Bruce-Robert Pocock 2011-09-04 00:01:50 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 236277 bytes
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\")' -load Miklee-em.lisp
comment: Unfortunately, I was working interactively and not sure what I did, precisely :-(
component: gcl
Attached file: coredump, 187203584 bytes
crash_function: error
executable: /usr/lib/gcl-2.6.8/unixport/saved_ansi_gcl
package: gcl-2.6.8-0.8.20110516cvs.fc14
rating: 4
reason: Process /usr/lib/gcl-2.6.8/unixport/saved_ansi_gcl was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
How to reproduce: Probably my fault (in a way) in attempting to define a badly-written DEFMETHOD PRINT-OBJECT … but, I don't think it should have crashed, just errored out?
time: 1315094299
uid: 500

Comment 1 Bruce-Robert Pocock 2011-09-04 00:01:52 UTC
Created attachment 521352 [details]
File: backtrace

Comment 2 Jerry James 2011-09-06 15:13:51 UTC
From the backtrace, it looks like formatted output was being produced when a type error was encountered (frame 483).  The active error handler tried to print some objects (presumably for an error message), apparently including the one whose PRINT-OBJECT method included the type error, which triggered the same type error again (frame 442).  The active error handler tried to print some objects ....

... and so on until stack space was exhausted, at which point GCL aborted.  I'm not at all sure this is a GCL bug.  What could GCL have done differently?

Comment 3 Jerry James 2011-10-29 17:52:17 UTC
I'm 99% sure this is a bug in the reporter's code, not GCL, and have not heard back from the reporter, so I'm closing this bug.

Note You need to log in before you can comment on or make changes to this bug.