http://qa.mandrakesoft.com/show_bug.cgi?id=5568
------- Additional Comments From [EMAIL PROTECTED] 2003-11-09 23:36 ------- SIG32 is caused by pthreads - it is used internally to notify a thread manager about some things inside of pthreads implementation. It is not a bug per se. This sets gdb to ignore it : handle SIG32 nostop noprint pass BTW, are you seeing also SIGTRAPs ? That is more interesting, since it breaks debugging of multi-threaded applications for me completely. I described the problems I have got here : http://qa.mandrakesoft.com/show_bug.cgi?id=4709 Usually I get SIG32, then set it to nostop,noprint, pass and immediately get SIGTRAP after typing continue. This usually hoses the debugger completely - no stacktrace, kill, quit do not work (hang) etc. -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: MythTV (http://www.mythtv.org) is a multi-threaded application. When debugging in gdb, gdb keeps raising SIG32 events, making it difficult to run / debug the application. Additionally, it appears that gdb does not always capture all thread stacks when a backtrace is performed. Not all versions of gdb created by Mandrake have had these issues when debugging multi-threaded applications, but because the segfaults are rare, it is difficult to remember exactly which gdb packages have had issues, and which don't. 5.3-25 definately has an issue with SIG32 events.
