created nautilus-scripts mimetype and scp_to_host from http://lagun.gnome-db.org/projects/nautilus-scripts/index.php, placed in /home/user/gnome2/nautilus-scripts, made scripts executable. when right click on file and select given script, script fails with crash dialog box referring to gdialog crashing. bug report also filed at bugzilla.gnome.org: http://bugzilla.gnome.org/show_bug.cgi?id=102985 inline bug report: Opened by lance_tt@bellsouth.net (Lance O. Lassetter) on 2003-01-09 17:18 Long Description Package: nautilus Severity: critical Version: 2.0.6 Synopsis: gdialog crashes with mimetype nautilus-script Bugzilla-Product: nautilus Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.0.6) Description: Description of Problem: gdialog crashes when executing mimetype nautilus-script (http://lagun.gnome-db.org/projects/nautilus-scripts/mimetype) Steps to reproduce the problem: 1. save http://lagun.gnome-db.org/projects/nautilus-scripts/mimetype to text file 2. move file to /home/user/.gnome2/nautilus-scripts and make executable 3. right click file in nautilus and select 'mimetype' under 'scripts' Actual Results: gdialog crash box comes up Expected Results: mimetype to be displayed properly How often does this happen? every time Additional Information: System is Gentoo 1.4rc1, gnome-utils package is 2.0.6, gnome package is gnome-2.0.3-r1 Please contact me if you need any more information. Debugging Information: Backtrace was generated from '/usr/bin/gdialog' (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 16384 (LWP 24775)] (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x40907a99 in wait4 () from /lib/libc.so.6 #0 0x40907a99 in wait4 () from /lib/libc.so.6 #1 0x4098420c in __DTOR_END__ () from /lib/libc.so.6 #2 0x4075bba3 in waitpid () from /lib/libpthread.so.0 #3 0x4006fc99 in libgnomeui_module_info_get () from /usr/lib/libgnomeui-2.so.0 Thread 1 (Thread 16384 (LWP 24775)): #0 0x40907a99 in wait4 () from /lib/libc.so.6 No symbol table info available. #1 0x4098420c in __DTOR_END__ () from /lib/libc.so.6 No symbol table info available. #2 0x4075bba3 in waitpid () from /lib/libpthread.so.0 No symbol table info available. #3 0x4006fc99 in libgnomeui_module_info_get () from /usr/lib/libgnomeui-2.so.0 No symbol table info available. #0 0x40907a99 in wait4 () from /lib/libc.so.6 ------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-01-09 17:17 ------- Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
*** Bug 13819 has been marked as a duplicate of this bug. ***
Try turning down optimisations, can't reproduce it.
Ok, use default that come in /etc/make.conf for i686 is it? And not use 'athlon-xp' optimisations? Also what should I rebuild with new optimisations? I tried rebuilding just gnome-utils, same error. Gnome seems very picky with cpu optimisations, this isn't the first time I've ran into this.
just try something like "-O1 -pipe" thats low can you figure out where gdiag crashes, get a backtrace with symbols maybe ?
Created attachment 7388 [details] strace of gdialog crashing Included as attachment is strace of gdialog crashing.
What should I re-emerge with lesser compiler optimisations? Tried emerging gnome-utils with just: CHOST="i686-pc-linux-gnu" CFLAGS="-march=athlon-xp -O3 -pipe" CXXFLAGS="-march=athlon-xp -O3 -pipe" or do I need to tune this down as well?
Yes you should, for a generic system thats pretty much ('generic' as in 'non-gentoo linux systems'). a gdb backtrace please, strace doesnt reveal all that much.
ok, have gdb installed but having problems creating a backtrace. what i'm testing with is # /usr/bin/gdialog --msgbox test 100 100 how would I create a gdb backtrace with this or would it be something different? I can get to a (gdb) prompt ok. Also when you say generic as in 'generic' Linux cpu optimisation flags, can I just comment out all optimisations in /etc/make.conf , that would set at default?
Edited /etc/make.conf, uncommented all lines for CFLAGS, CXXFLAGS, set first optimisiation line to: CHOST="i686-pc-linux-gnu" recompiled and installed gnome, gnome-utils still gdialog can't bring up nautilus-scripts then tried CHOST="i386-pc-linux-gnu" recompiled and installed gnome, gnome-utils yet again doesn't work need info on using gdb with gdialog and if this was done right
set CFLAGS and CXXFLAGS to "-g -pipe", recompile, then do $ gdb /usr/bin/gdialog (gdb) run --msgbox test 100 100 program blah recieved sigsegv (gdb) bt
Created attachment 7529 [details] requested gdb output as given instructions: set CFLAGS and CXXFLAGS to "-g -pipe", recompile, then do $ gdb /usr/bin/gdialog (gdb) run --msgbox test 100 100 program blah recieved sigsegv (gdb) bt completed with attached text file result
is this still a problem with latest gnome-utils (2.2.0.3) btw?
Created attachment 8920 [details] Backtrace of gdiag crash. Yes, it still isnt' working, even with gnome-utils-2.2.0.3 Attached is backtrace, although I don't know if it will be helpful.
not really, can you add 'inherit debug' at the top of the ebuild and build it without any optimizations (just CFLAGS="") and give us the resulting backtrace ?
Created attachment 9158 [details] backtrace with set 'inherit debug' in gnome-utils ebuild As requested, backtrace of gdialog segfault with 'inherit debug' in ebuild as well as CFLAGS=""
from the backtrace, it looked like it was ncurses that was producing the segfault. do you want to try re-emergeing that?
seems to be fixed, no more msg from bug-reporter
Apparently, it was the nautilus-scripts that were borked. Sorry haven't responded sooner, thanks.
