GNOME Bugzilla – Bug 114004
Intermittent segmentation fault
Last modified: 2004-12-22 21:47:04 UTC
Package: gedit Severity: normal Version: 2.2.0 Synopsis: Intermittently receive "segmentation fault"-related alert messages ,and the messages would quickly go away.. Today, I was able to capture the alert message and goes something like this: "Application "gedit(proces 5623) has crashed due to fatal error(segmentation fault)" Bugzilla-Product: gedit Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: I have 3 terminal sessions open and a test editor and switching from them all the time, then suddenly received this alert message "segmentation fault". Is that error interface related or something else? Steps to reproduce the problem: 1. 2. 3. Actual Results: This is the actual error message: Application "gedit(process 5623)" has crashed due to fatal error(segmentation fault). Expected Results: How often does this happen? intermittently Additional Information: Common alert message is "segmentation fault" but not sure if the previous ones are related to gedit. Debugging Information: Backtrace was generated from '/usr/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)...[New Thread 1091449088 (LWP 5623)] (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)...0xffffe002 in ?? ()
+ Trace 37315
Thread 1 (Thread 1091449088 (LWP 5623))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-05-29 19:22 ------- Reassigning to the default owner of the component, maggi@athena.polito.it.
Shortening the summary. Also... This looks like the mysterious gtk+ crash that is showing up everywhere [See specifically bug 105745 for more info]. A number of people are getting this, but the stack traces are unfortunately useless and we don't know how to reproduce the problem. Can you get a stacktrace with symbols for us? [If you're using RedHat 9, you can do so with the following easy method; otherwise this will require recompiling from source: Install http://people.redhat.com/otaylor/tmp/gtk2-debuginfo-2.2.1-4.i386.rpm and if the problem occurs again, submit the backtrace you get. Installing the debuginfo package will make the backtrace much more useful.] I am adding myself to the cc and marking as needinfo for now.
If you have any more useful information about these crashes, please post them in bug 105745. *** This bug has been marked as a duplicate of 105745 ***