| Summary: | GnuCash abnormally exists after guile seg faults | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Philippe Laflamme <plaflamme> |
| Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | 1.4 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Philippe Laflamme
2003-11-26 19:42:49 UTC
After reading bug 114932 in Gnome's database (http://bugzilla.gnome.org/show_bug.cgi?id=114932), I remerged glibc. It fixed the problem. Maybe this should be investigated more thoroughly. i'm not sure how we can investigate further if it can't be duplicated any more. I'm inclined to think that it is a transient occurance with a particular revision of glibc? btw, why did you think it is caused by guile and also in the gnome bug report, it seems unconfirmed that the crash was caused by guile since their backtraces pointed to glib which isn't used by guile. In my initial post I mentioned the "root" cause of GnuCash exiting: "At this point, I get a Gnome popup window telling me /usr/bin/guile has seg faulted and GnuCash exits." A window poped up stating that the "/usr/bin/guile" application had a segmentation fault error. This is the only thing that pointed me to guile. I did not use gdb to come to this conclusion, so it might be erronous. It's still strange that remerging glibc fixed the problem. I don't understand how this could NOT have affected any other application besides guile or GnuCash (whichever was the one in cause here). That's why I mentioned it could be worth investigating. I agree, that this is probably a transient issue, maybe my emerge history could give an insight on what might have been the problem? Since this issue has been fixed and can't be reproduced anymore, i'm closing. |