On Tue, 25 Jul 2006 16:37:21 +0200, "Sascha Heid" saschaheid@gmail.com wrote:
Type "run --debug" instead of only "run", and then when it crashed and you got back to the gdb prompt, type "backtrace" and post the output. I just want to know where the double free is.
Ok, here it is:
Program received signal SIGABRT, Aborted. [Switching to Thread -1219442496 (LWP 20926)] 0xffffe410 in __kernel_vsyscall () (gdb) backtrace #0 0xffffe410 in __kernel_vsyscall () #1 0xb77a0641 in raise () from /lib/libc.so.6 #2 0xb77a1c99 in abort () from /lib/libc.so.6 #3 0xb77d532b in __fsetlocking () from /lib/libc.so.6 #4 0xb77dad20 in malloc_usable_size () from /lib/libc.so.6 #5 0xb77dc364 in free () from /lib/libc.so.6 #6 0xb79b6831 in g_free () from /usr/lib/libglib-2.0.so.0 #7 0x0819ae60 in ?? () #8 0x00000000 in ?? ()
Hmm, this is not so informative as I expected. Can you compile Geany with debug support? The important point is in the line 7,8 or even earlier. The lines in the backtrace are only the result of the error.
Regards, Enrico
-- Get my GPG key from http://www.uvena.de/pub.key