GNOME Bugzilla – Bug 326184
gnome-nettool 1.4.1 segfaults when called from the commandline with wrong or incomplete arguments.
Last modified: 2006-03-16 10:20:54 UTC
Forwarded from: http://bugzilla.ubuntu.com/show_bug.cgi?id=18097 gnome-nettool 1.4.1 segfaults when called from the commandline with wrong or incomplete arguments. Works: $ gnome-nettool -l www.aap.nl $ gnome-nettool -p www.aap.nl $ gnome-nettool --ping=www.aap.nl $ gnome-nettool --ping= The latter options pops up a window "a network address was not specified". Nice! Segmentations fault occur with: $ gnome-nettool -l $ gnome-nettool -p $ gnome-nettool --ping $ gnome-nettool -help $ gnome-nettool --random-string This is not a catastrophic bug, but it's a bug.
+ Trace 65033
Thread 1 (Thread 46912547468496 (LWP 31265))
I have already filed a comment on ubuntu (https://launchpad.net/distros/ubuntu/+source/gnome-nettool/+bug/24242) where I mentioned that I suspect the problem to relate to my WLAN driver. Now I thought the following gdb output might be useful: (gdb) run Starting program: /usr/bin/gnome-nettool [...] [Thread debugging using libthread_db enabled] [New Thread -1219249568 (LWP 11742)] [...] *** glibc detected *** double free or corruption (!prev): 0x0829ab00 *** Program received signal SIGABRT, Aborted.
+ Trace 66112
Thread NaN (LWP 11742)
Created attachment 61315 [details] [review] patch fix the issue by handling failure of gtk_init_with_args
Patch committed to HEAD