Description:
I was trying to debug a QT-based application in KDevelop using the embedded GDB frontend
but even though the application ran fine it was impossible to debug due the continuous
SIGTRAP signals emitted by system libs and intercepted by the debugger.
Here is a sample of error:


Program received signal SIGTRAP, Trace/breakpoint trap.
0xb7f67d81 in malloc () from /lib/ld-linux.so.2
The program being debugged was signaled while in a function called from GDB.
GDB remains in the frame where the signal was received.
To change this behavior use "set unwindonsignal on"
Evaluation of the expression containing the function (malloc) will be abandoned.


The command "set unwindonsignal on" suppressed the error dialogs but most variables
became corrupted and made the QT program to crash or not to behave as expected.

I solved the problem installing the 2.6.25 kernel from kernel.org and compiling it
by myself (using the old .config file). Now everything work as expected.


Additional info:

extra/KDevelop 3.5.1-1
extra/gdb 6.7.1-1
Default kernel 2.6.24-ARCH provided with the standard core Arch Linux installation
core/glibc 2.7-9


Steps to reproduce:
Try to set breakpoints and step over some instructions in any QT based application
(the examples and tutorials provided in the QT Official Documentation for instance).
I don't know if this bug is extended to simple C/C++ debugging.

I'm attaching the GDB output during the debug.