Re: Problems with glibc-2.2.2 and threads (realtime signal)

2001-03-20 Thread Henning Baldersheim
Hi I just attached to the newsgroup so I do not have the start of this thread. The answer might also be the answer to my problem. I am debugging a multithreaded application, but I am not able to get going because half way through the startup procedure the application is terminated with the

Re: Problems with glibc-2.2.2 and threads (realtime signal)

2001-03-20 Thread Kevin Buettner
On Mar 20, 1:23pm, Henning Baldersheim wrote: I am debugging a multithreaded application, but I am not able to get going because half way through the startup procedure the application is terminated with the message: thread_db: map_id2thr failed: invalid thread handle Then there is no

Re: Problems with glibc-2.2.2 and threads (realtime signal)

2001-03-16 Thread bart . durinck
Hi! I think I found some info that might explain your problem. It could well be that it's not GDB's fault, but some system libraries being stripped. Mandrake Linux 7.2 is known to have this problem. Bug-report 1763 "GDB cannot debug programs that use shared libraries or threads" explains (see

Re: Problems with glibc-2.2.2 and threads (realtime signal)

2001-03-08 Thread bart . durinck
Hi! In my experience this is a known feature. It is gdb's (4.18 and 5.0) default setting to intercept this SIG 32 RealTime signal. glibc (since 2.1.2 or 2.1.3) uses this signal for threading, so that explains what is happening. You can work-arond this by using the 'handle' command. Do: