peter kostov wrote: > Martin Nordholts wrote: >> peter kostov wrote: >>> Or if I run GIMP so: >>> pe...@peter ~ $ gimp --g-fatal-warnings --stack-trace-mode=always >>> --debug-handlers >>> >>> GLib-GObject-WARNING **: type name `GimpGeglTool-gegl:box-blur-config' >>> contains invalid characters >>> aborting... >>> gimp: terminated: Aborted >>> #0 0xb7f4c424 in __kernel_vsyscall () >>> #1 0xb75d0f9b in waitpid () from /lib/libpthread.so.0 >>> #2 0xb75ef577 in g_on_error_stack_trace () from >>> /usr/lib/libglib-2.0.so.0 >>> #3 0x00000011 in ?? () >>> #4 0x0b2ce178 in ?? () >>> #5 0x00000001 in ?? () >>> #6 0x00000000 in ?? () >>> >>> (script-fu:1936): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): >>> error >>> >>> >>> Peter >> >> That was not the entire stack trace was it? Make sure you have debugging >> information in the binary, i.e. make sure the -g flag is passed to gcc. >>
O.K. This time I did the backtrace properly, unfortunately there is nothing more. Below is the whole backtrace.log file from gdb: Starting program: /usr/bin/gimp --verbose --g-fatal-warnings --stack-trace-mode=always --debug-handlers [Thread debugging using libthread_db enabled] [New Thread 0xb72e06c0 (LWP 20896)] [New Thread 0xb71a6b90 (LWP 20900)] [New Thread 0xb69a5b90 (LWP 20901)] Program received signal SIGABRT, Aborted. [Switching to Thread 0xb72e06c0 (LWP 20896)] 0xb7f55424 in __kernel_vsyscall () quit The program is running. Exit anyway? (y or n) And GIMP hangs. Any help is appreciated! Peter _______________________________________________ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
