http://qa.mandrakesoft.com/show_bug.cgi?id=5568
------- Additional Comments From [EMAIL PROTECTED] 2003-20-09 16:27 ------- The main test is to check if info threads returns a list of running threads and that you can change from one thread to another by using the thread n (where n is the thread number) command. Try a bt on each thread to confirm that each thread has its own context. I fixed this on my Mandrake 9.0 by recompiling glibc from the .srpm then copying the unstripped pthread libraries over the top of my existing pthread libraries which I had backed up first. After a quick reboot cos this was quick and dirty, gdb worked fine on my threaded apps. I notice that the spec file for the glibc srpm did not have the pthread libraries in the no strip section - that should be the only required change. -- 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: NEW 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.
