Hello,
I'm trying to debug some multithreaded apps, I'm using gdb-5.0 and
glibc-2.2.2. GDB works without problems for non-threaded apps, but whenever
I try to debug a threaded one I got "SIG32, Real-time event 32" instead of
the signal that would tell gdb that a new threaded is created. Anybody has
also experiment this? Is this a GDB bug? a GLibc bug? or a kernel related
problem? (kernel has NO bugs :-)
I'm using 2.4.2-ac13, but it also happens with 2.4.2, and later,
doesn't check with previous kernels.
Regards,
- german
PS: Please CC'd to me as I'm not subscribed to the mailing list. Thanks.
-------------------------------------------------------------------------
German Gomez Garcia | "This isn't right. This isn't even wrong."
<[email protected]> | -- Wolfgang Pauli
On Wed, 7 Mar 2001 17:46:09 +0100 (CET) German Gomez Garcia <[email protected]> wrote:
> Hello,
>
> I'm trying to debug some multithreaded apps, I'm using gdb-5.0 and
> glibc-2.2.2. GDB works without problems for non-threaded apps, but whenever
> I try to debug a threaded one I got "SIG32, Real-time event 32" instead of
> the signal that would tell gdb that a new threaded is created. Anybody has
> also experiment this? Is this a GDB bug? a GLibc bug? or a kernel related
> problem? (kernel has NO bugs :-)
>
> I'm using 2.4.2-ac13, but it also happens with 2.4.2, and later,
> doesn't check with previous kernels.
Reading the ChangeLog for glibc-linuxthreads I found something about
ASSUME_REALTIME_SIGNALS being undef by default, I'm currently recompiling
the C library with it enabled, more info later ...
- german
-------------------------------------------------------------------------
German Gomez Garcia | "This isn't right. This isn't even wrong."
<[email protected]> | -- Wolfgang Pauli