public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: German Gomez Garcia <german@piraos.com>
To: kernel <linux-kernel@vger.kernel.org>
Subject: Re: Problems with gdb and latest kernels (SIG32)
Date: Wed, 7 Mar 2001 17:52:43 +0100 (CET)	[thread overview]
Message-ID: <20010307165243.669.qmail@piraos.com> (raw)


On Wed, 7 Mar 2001 17:46:09 +0100 (CET) German Gomez Garcia <german@piraos.com> 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."
<german@piraos.com>         |                         -- Wolfgang Pauli



             reply	other threads:[~2001-03-07 16:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-07 16:52 German Gomez Garcia [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-03-07 16:46 Problems with gdb and latest kernels (SIG32) German Gomez Garcia

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010307165243.669.qmail@piraos.com \
    --to=german@piraos.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox