public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Brian Budge" <brian.budge@gmail.com>
To: gdb@sourceware.org
Subject: Re: info threads
Date: Mon, 03 Dec 2007 21:29:00 -0000	[thread overview]
Message-ID: <5b7094580712031329o7754410el60dc06e8b1af2078@mail.gmail.com> (raw)
In-Reply-To: <20071202235626.GA10030@caradoc.them.org>

Thanks for the pointer.  This was on Gentoo Linux, and libpthread was
indeed stripped.  I recompiled glibc with FEATURES="nostrip", and
everything works great.

Thanks again,
  Brian

On Dec 2, 2007 3:56 PM, Daniel Jacobowitz <drow@false.org> wrote:
> On Sun, Dec 02, 2007 at 03:09:04PM -0800, Brian Budge wrote:
> > Hi all -
> >
> > I'm having trouble with some of the threading interfaces of gdb.  For
> > instance, info threads prints nothing.  I have read that this means it
> > is not supported for my architecture, but I could have sworn it worked
> > before.  That being said, I switched over from x86 to x86_64 a few
> > months ago, so maybe it's just my failing memory.
>
> Architecture has nothing to do with this.  You didn't say, but I'm
> guessing you mean some distribution of GNU/Linux, right?  In that
> case, this usually means that your libpthread.so or ld.so have been
> stripped, and that separate debug files for them are not available.
>
> --
> Daniel Jacobowitz
> CodeSourcery
>

  reply	other threads:[~2007-12-03 21:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-02 23:09 Brian Budge
2007-12-02 23:56 ` Daniel Jacobowitz
2007-12-03 21:29   ` Brian Budge [this message]
2007-12-04  3:30     ` Michael Snyder
2007-12-04 17:10       ` Jim Blandy
2007-12-04 19:22         ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2003-05-08 13:25 John S. Yates, Jr.
2003-06-06 21:31 ` Andrew Cagney

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=5b7094580712031329o7754410el60dc06e8b1af2078@mail.gmail.com \
    --to=brian.budge@gmail.com \
    --cc=gdb@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).