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:

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: SIG32 with Linux and pthreads

2001-05-28 Thread bart . durinck
... For that you need a recent GDB straight from CVS... Good luck! Bart Bart Durinck 03/16/2001 10:59 AM To: German Gomez Garcia [EMAIL PROTECTED] cc: [EMAIL PROTECTED] Subject: Re: Problems with glibc-2.2.2 and threads (realtime signal) (Document link: Database 'Bart Durinck', View

The thread/float/NaN bug in GDB 5.1, a survey

2001-12-07 Thread bart . durinck
Hi! I _also_ found the the thread/float/NaN bug in GDB. But Kevin Buettner beat me in supplying the patch... I saw Kevin's message while I was preparing this message. How funny/strange two people find the same bug at the same moment when it's been there for half a year... But I am not sending