From: Daniel Jacobowitz <drow@false.org>
To: Michael Shuldman <michael.shuldman@ericsson.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdb, target remote, threadbased application in uml
Date: Wed, 28 Feb 2007 14:11:00 -0000 [thread overview]
Message-ID: <20070228133452.GA10900@caradoc.them.org> (raw)
In-Reply-To: <20070228132456.GA31886@localhost>
On Wed, Feb 28, 2007 at 02:24:56PM +0100, Michael Shuldman wrote:
> Daniel Jacobowitz wrote,
> > > [Thread debugging using libthread_db enabled]
> > > [New Thread 1076389568 (LWP 765)]
> > > Can't attach LWP 765: No such process
> >
> > That shouldn't happen, but you haven't said what version of GDB you're
> > using. You may wish to try a newer one.
>
> Oops, sorry I forgot that.
> linux-gnu/i486 0$ gdb -version
> GNU gdb 6.4-debian
I don't remember such a bug in 6.4, but the current release is 6.6;
please try that. The packages from Debian/unstable ought to work.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-02-28 13:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 13:25 Michael Shuldman
2007-02-28 13:35 ` Daniel Jacobowitz
2007-02-28 13:47 ` Michael Shuldman
2007-02-28 14:11 ` Daniel Jacobowitz [this message]
2007-02-28 21:16 ` Michael Shuldman
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=20070228133452.GA10900@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=michael.shuldman@ericsson.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