GNOME Bugzilla – Bug 127845
GEdit segfault
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Unknown Package: gedit Severity: normal Version: GNOME2.4.0 2.4.0 Gnome-Distributor: Gentoo Linux Synopsis: GEdit segfault Bugzilla-Product: gedit Bugzilla-Component: general Bugzilla-Version: 2.4.0 BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: Quick turning line-numbering on-off-on causes gedit to segfault. Steps to reproduce the crash: 1. See above. 2. 3. Expected Results: I expected line-numbering to be turned on and off without a crash =) How often does this happen? Often Additional Information: 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)...[New Thread 16384 (LWP 2970)] (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)...0x4051c1c7 in waitpid () from /lib/libpthread.so.0
+ Trace 42048
Thread 1 (Thread 16384 (LWP 2970))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-11-24 17:00 ------- Unknown version 2.4.0 in product gedit. Setting version to the default, "unspecified". The original reporter (oyvinst@ifi.uio.no) 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 helps to have a lot of files opened at once, to trigger the bug.
What level of optimization are you compiled with? What version of gtk are you using? Are you compiling in any extra patches? This looks like it might be a duplicate of bug 120118, but I'm not sure.
At the time of compilation I think I used CFLAGS="-march=pentium3 -O2 -fomit-frame-pointer". The bug is really much simpler to trigger than I indicated earlier. There is no need to have any open documents. Just go into Prefs, enable line numbers, then disable them again => segfault. Gtk version is 2.2.4 (glib 2.2.3). There are extra patches applied by the Gentoo ebuild script. After some investigation I think these are included: # the wrong symbols gtk+-2.0.6-exportsymbols.patch # should speed up metacity gtk+-wm.patch # bautifying patch for disabled icons disable_icons_smooth_alpha.patch # xft/slighthint stuff from RH xftprefs.patch # notification area loop fix (http://bugs.gnome.org/show_bug.cgi?id=122327) # submitted by <pat@engsoc.org> 2.2-notificationarea_loop.patch And yes, this is in fact a duplicate of bug # 120118 (just checked it out). I don't use aggressive optimalization options.
*** This bug has been marked as a duplicate of 120118 ***
Øyvind Stegard: For future reference, -fomit-frame-pointer makes stack traces useless. Please recompile without that option to obtain useful stack traces. I suspect one of the gtk+ patches may be at fault, so if I were to try to track it down, I'd start by removing those to see if they helped. Anyway, just some food for thought. I'll let the rest of the discussion (if there be any) go on in bug 120118.