From: "Peter Berger" <peterb@telerama.com>
To: "Kevin Buhr" <buhr@stat.wisc.edu>
Cc: <linux-kernel@vger.kernel.org>, "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
Subject: Re: Pthreads, linux, gdb, oh my! (fwd)
Date: Sat, 9 Dec 2000 10:15:08 -0500 [thread overview]
Message-ID: <000f01c06253$3ba12cc0$a600000a@toucan> (raw)
In-Reply-To: <Pine.BSI.4.02.10012081150130.17198-100000@frogger.telerama.com> <vbasnny3xy9.fsf@mozart.stat.wisc.edu>
.
> It looks like a GDB bug. GDB contains code to recognize when the
> "pthreads" shared library has been loaded. When this happens, it sets
> itself up to properly handle threads (including setting up correct
> SIG32 signal handling). If you trick GDB into thinking "pthreads"
> hasn't been loaded and set the SIG32 stuff up yourself, like so:
[elided]
Kevin,
This sure looks like it -- I was able to get it working using your
technique. Thank you! It is a relief to know that this was just an
application layer issue rather than something deeper.
My apologies for soaking up cycles on linux-kernel for what turned out to be
a non-kernel issue -- but a big THANKS to everyone that helped track the
problem down -- let me know the next time you're in Pittsburgh, and I'll buy
you a beer (or the beverage of your choice).
-p
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-10 3:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-08 16:53 Pthreads, linux, gdb, oh my! (fwd) Peter Berger
2000-12-08 17:18 ` Alan Cox
2000-12-08 19:43 ` Peter Berger
2000-12-09 0:02 ` Alan Cox
2000-12-09 6:34 ` Kevin Buhr
2000-12-09 15:15 ` Peter Berger [this message]
[not found] <Pine.BSI.4.02.10012081708350.130-100000@frogger.telerama.c om>
2000-12-08 21:21 ` Petr Vandrovec
2000-12-08 22:15 ` Peter Berger
2000-12-08 22:31 ` David Relson
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='000f01c06253$3ba12cc0$a600000a@toucan' \
--to=peterb@telerama.com \
--cc=VANDROVE@vc.cvut.cz \
--cc=buhr@stat.wisc.edu \
--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