From: "H . J . Lu" <hjl@lucon.org>
To: Duncan Palmer <duncan.palmer@s3group.com>
Cc: GDB <gdb@sourceware.cygnus.com>
Subject: Re: RFC: Fix gdb 5.1 for Linuxthreads
Date: Wed, 19 Sep 2001 09:19:00 -0000 [thread overview]
Message-ID: <20010919091925.G30455@lucon.org> (raw)
In-Reply-To: <3BA892A0.3E6D56C3@s3group.com>
On Wed, Sep 19, 2001 at 01:42:08PM +0100, Duncan Palmer wrote:
> I've just given your patch a try, and it works well for me. I have
> another thread related problem with gdb 5.1 however - if i start my
> application from within gdb, or attach to any threads of the process,
> 'info threads' gives me back nothing despite the fact that there are
> quite a few threads running - this works fine when i use the version of
> gdb 4.18 that comes with Mandrake (i assume its the same as comes with
> RedHat, but i'm not sure if it has thread related patches applied or
> not).
>
> I'm using glibc 2.1.3 and libpthreads 0.8 on x86
>
I didn't see your problem. Please try glibc 2.2 and kernel 2.4 to see
if it goes away.
H.J.
next prev parent reply other threads:[~2001-09-19 9:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-17 12:47 Is the current gdb 5.1 broken for Linuxthreads? H . J . Lu
[not found] ` <20010917161350.A25349@lucon.org>
2001-09-17 19:13 ` H . J . Lu
2001-09-18 13:56 ` H . J . Lu
2001-09-18 15:22 ` RFC: Fix gdb 5.1 for Linuxthreads H . J . Lu
2001-09-19 5:42 ` Duncan Palmer
2001-09-19 9:19 ` H . J . Lu [this message]
2001-09-20 8:21 ` Duncan Palmer
2001-09-19 7:06 ` Mark Kettenis
2001-09-19 8:58 ` H . J . Lu
2001-09-19 0:46 ` Is the current gdb 5.1 broken for Linuxthreads? Eli Zaretskii
2001-09-19 8:43 ` H . J . Lu
2001-09-19 6:56 ` Mark Kettenis
2001-09-19 7:39 ` Eric Paire
2001-09-19 9:05 ` H . J . Lu
2001-09-20 0:59 ` Eric Paire
2001-09-19 13:39 ` Andrew Cagney
2001-09-20 1:36 ` Eric Paire
2001-09-20 8:03 ` H . J . Lu
2001-09-20 21:49 ` Eric Paire
2001-09-19 9:10 ` H . J . Lu
2001-09-19 6:32 ` Mark Kettenis
2001-09-19 9:16 ` H . J . Lu
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=20010919091925.G30455@lucon.org \
--to=hjl@lucon.org \
--cc=duncan.palmer@s3group.com \
--cc=gdb@sourceware.cygnus.com \
/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