This is the mail archive of the
mailing list for the GDB project.
Re: Program received signal SIG33, Real-time event 33.
Daniel Jacobowitz wrote:
On Sun, Sep 02, 2007 at 12:50:46AM -0700, Petr Vandrovec wrote:
Apparently your program uses signals... If this is expected (which probably is
for realtime signals) then
handle SIG33 nostop noprint pass
will configure gdb so this signal is ignored by gdb, but delivered to program
like without gdb.
No, SIG33 is generally internal to the threading implementation.
GDB 6.3 is somewhat old. I recommend trying a current version.
If Ying uses setuid() from multithreaded program then I think that glibc
has more than one surprise ready for him...