GNOME Bugzilla – Bug 106244
Gedit crashes on exit
Last modified: 2004-12-22 21:47:04 UTC
Package: gedit Severity: critical Version: GNOME2.2.0 2.2.0.1 os_details: Gnome.Org Synopsis: Gedit crashes on exit Bugzilla-Product: gedit Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: Gedit works normally (with/without plugins) but as soon as you exit, it crashes. Steps to reproduce the problem: 1. Open Gedit 2. Close it 3. It crashes Actual Results: gedit coredumps on exit. Expected Results: gedit coredumps/crashes on exit How often does this happen? Always Additional Information: Tried recompiling several times, still no luck. Debugging Information: Backtrace was generated from '/usr/X11R6/bin/gedit' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x28f8dcb8 in __sys_poll () from /usr/lib/libc_r.so.4
+ Trace 33901
Thread 1 (process 96467, thread 1)
#3 0x0 in ?? () No symbol table info available. ------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-02-16 14:14 ------- The original reporter (terminus@qubix.ca) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, maggi@athena.polito.it.
It looks like the stack trace was truncated. Can you submit a complete stack trace? (Please see http://bugzilla.gnome.org/getting-traces.cgi for more information on how to do this.)
I apologize for the spam, but in talking to David Kennedy on #bugs we decided that it might be useful for me to add a comment to a lot of bugs that have nearly identical stack traces that aren't very useful. (It took me a while because I gave up on several bugzilla queries that simply hung). Anyway, I may have caught some bugs with this query that aren't relevant, so I apologize again if this bug is one of those. If not: The following comment from 100709 may be relevant: "It turns out this was an accidental FreeBSD ABI change during the import of gcc-3.2.1. div(), a structure returning function, was the culprit."
*** This bug has been marked as a duplicate of 100709 ***