--stack-trace-mode doesn’t seem to work

Thank you for taking the time to report this bug and helping to make Ubuntu better. that option helps you to debug gimp it doesnt prevent gimp to crash. you might want to read about https://wiki.ubuntu.com/DebuggingProgramCrash ; thanks.

Gimp crashes. It catches the SEGV using its own handler, so apport and gdb don’t catch it. A parameter should prevent gimp from catching the signal. The parameter doesn’t work. How is this invalid?

Did you read it the info i posted here?, it contains instructions on how to debug an application. If you want to debug gimp with their own tools you should run: gimp --debug-handlers --stack-trace-mode always

‘--stack-trace-mode never’ doesn’t work, it’s as simple as that.

I don’t believe my debugging intentions or someone’s misunderstanding of them matters regarding the validity of this bug report.

This shouldn’t happen:

% gimp --stack-trace-mode never
This is a development version of GIMP. Debug messages may appear here.

*** glibc detected *** gimp: double free or corruption (out): 0x090d7850 ***
======= Backtrace: =========
/lib/tls/i686/cmov/libc.so.6[0xb76c8d75]
/lib/tls/i686/cmov/libc.so.6(cfree+0x90)[0xb76cc810]
/usr/lib/libglib-2.0.so.0(g_free+0x31)[0xb77f78c1]
and so on.

i don't see how it doesn't work for you Johan, it works pretty well here, i'm able to debug gimp with gdb and obtain all the needed info to get a good trace.

I investigated the problem a bit further. It isn’t a segmentation fault, but instead libc detects a problem, prints a stack trace and calls abort().

When using ‘--stack-trace-mode never’, gimp refrains from catching SIGBUS, SIGSEGV and SIGFPE, but it still catches SIGABRT, which isn’t then raised for apport to catch.

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest version of Ubuntu - the Hardy Heron.