From: Daniel Jacobowitz <drow@false.org>
To: Ajay Patel <ajayp@kymasys.com>
Cc: gdb@sources.redhat.com
Subject: Re: unable to debug statically linked program with linux threads
Date: Fri, 18 Mar 2005 02:47:00 -0000 [thread overview]
Message-ID: <20050318024745.GA26767@nevyn.them.org> (raw)
In-Reply-To: <1111103952.21230@horse.he.net>
On Thu, Mar 17, 2005 at 03:59:12PM -0800, Ajay Patel wrote:
> Daniel,
>
> I checked out gdb from CVS head and applied this
> "http://sourceware.org/ml/gdb-patches/2004-12/msg00240.html"
> patch.
>
> But still no thread commands.
I'm afraid you'll need the second patch referenced in that message; I
haven't submitted it to gdb-patches yet - thought I had. I will be
doing that after this patch is approved, or you can try the Debian
source package which includes the patch.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-03-18 2:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 23:59 Ajay Patel
2005-03-18 2:47 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-18 23:53 Ajay Patel
2005-03-17 22:07 Ajay Patel
2005-03-17 22:13 ` Daniel Jacobowitz
2005-03-17 22:19 ` Eric Desjardins
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=20050318024745.GA26767@nevyn.them.org \
--to=drow@false.org \
--cc=ajayp@kymasys.com \
--cc=gdb@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).