GNOME Bugzilla – Bug 333482
crash with command completion
Last modified: 2006-07-16 20:20:36 UTC
To reproduce: - Login on a server - Type: /AL <tab> Starting program: /home/cassidy/gnome/xchat-gnome/src/fe-gnome/xchat-gnome [Thread debugging using libthread_db enabled] [New Thread 1996261056 (LWP 11635)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1996261056 (LWP 11635)] 0x77329682 in malloc_usable_size () from /lib/tls/i686/cmov/libc.so.6 (gdb) thread apply all bt
+ Trace 66702
Thread 1 (Thread 1996261056 (LWP 11635))
I can't reproduce, and the trace looks odd. Is this still happening?
Yep, i still have this issue (with the same trace). In fact it doesn't really crash, it's "just" the app that freeze. I use gdb to get the trace.
GRRRR i really don't understand this bug. *** glibc detected *** corrupted double-linked list: 0xb7335358 *** Program received signal SIGABRT, Aborted. Seems this crash doesn't occur if the g_free in text-entry.c:476 is removed but i can't see any reason to explain that.
Perhaps valgrind could help?
RAHHH shame on me !! I'm completely stupid !!! It was just that the npt pointer was freed two times ... Fixed in the development version. The fix will be available in the next major release. Thank you for your bug report.