Red Hat Bugzilla – Bug 449208
nm-applet crashes when clicking on "connection information"
Last modified: 2008-11-02 17:06:46 EST
Description of problem:
nm-applet segfaults when the user clicks on "connection information" menu option.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Right-click on NM icon
2. Select "Connection Information"
Program received signal SIGSEGV, Segmentation fault.
0x00ac7053 in malloc_consolidate () from /lib/libc.so.6
#0 0x00ac7053 in malloc_consolidate () from /lib/libc.so.6
#1 0x00ac8e1d in _int_malloc () from /lib/libc.so.6
#2 0x00acac55 in malloc () from /lib/libc.so.6
#3 0x001504b4 in g_malloc () from /lib/libglib-2.0.so.0
#4 0x00167013 in g_slice_alloc () from /lib/libglib-2.0.so.0
#5 0x00512c89 in pango_script_iter_new () from /usr/lib/libpango-1.0.so.0
#6 0x00500457 in ?? () from /usr/lib/libpango-1.0.so.0
#7 0x005014d8 in pango_itemize_with_base_dir () from /usr/lib/libpango-1.0.so.0
#8 0x00509cb9 in ?? () from /usr/lib/libpango-1.0.so.0
#9 0x0050b1bb in ?? () from /usr/lib/libpango-1.0.so.0
#10 0x07b687a7 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#11 0xbfd0adec in ?? ()
#12 0x00000000 in ?? ()
Crash shouldn't happen
Created attachment 307267 [details]
Detailed failure stack trace after stepping through the code
After stepping through the failing code with gdb, I got a different stack
Looks like memory corruption actually; could you run the applet through valgrind
and then click on Connection Information and attach the valgrind output?
Created attachment 308175 [details]
valgrind error report when clicking "connection information".
It's an invalid free(). When running under valgrind the crash didn't happen -
probably valgrind prevented the actual freeing wrong memory from happening, the
dialog opened properly.
Nice catch and thanks!! for the valgrind log. Should be fixed in an update to
NM since that code has been changed since svn3623 and as a side-effect the bug
has been removed. The commit went in after what's in f9-updates-testing
(svn3675 I believe) so it won't be fixed there yet.
Please test with latest NM updates (svn4022 or later), thanks!