bug-gdb
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: bart . durinck
Subject: Re: Problems with glibc-2.2.2 and threads (realtime signal)
Date: Thu, 8 Mar 2001 17:40:02 +0100

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:

(gdb) handle SIG32 nostop
(gdb) handle SIG32 noprint

This will probably result in the behaviour you're looking for.

(gdb) help handle

This will explain in a bit more detail.

If you're using DDD (If you don't, try it!), you can use "Signals..."
dialog under the Status menu-item.

Good luck!

Bart





German Gomez Garcia <address@hidden>@gnu.org on 03/08/2001 03:25:26 PM

Sent by:  address@hidden


To:   address@hidden
cc:

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



        Hello,

        I'm trying to debug a multithreaded application, but I'm not able
to
make gdb work with it. I've tried gdb-4.17, gdb-4.18 and gdb-5.0 (currently
compiling CVS) but I always get the same, when running the program I get
SIG32 RealTime signals that stop gdb, even before the first
pthread_create(), and of course I'm not able to trace or set breakpoints, I
just get lots of SIG32. If I recompile the glibc-linuxthreads-2.2.2
undefining ASSUME_REALTIME_SIGNALS gdb works again. I would like to know if
this problem is already known, and if there is any fix for it.

        Thanks

        - german

PS: Please CC to me as I'm not subscribed to this mailing list.
-------------------------------------------------------------------------
German Gomez Garcia         | "This isn't right.  This isn't even wrong."
<address@hidden>         |                         -- Wolfgang Pauli



_______________________________________________
Bug-gdb mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/bug-gdb






reply via email to

[Prev in Thread] Current Thread [Next in Thread]