Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: B Mullins <mul.web06@gmail.com>
To: gdb@sourceware.org
Cc: mul.web06@gmail.com
Subject: Fwd: Thread Debugging - NPTL/PPC
Date: Sun, 06 Nov 2005 18:52:00 -0000	[thread overview]
Message-ID: <ba824fa10511061052h3e3ee17cmc75a1b4d7a54cf3e@mail.gmail.com> (raw)
In-Reply-To: <ba824fa10511061049l746105adg34641d3ca477f91a@mail.gmail.com>

I have two boards, one is a ppc, one is a ppc64.  On both boards I
have 32 bit libs.  Using the exact same libs and binaries on the ppc
as the ppc64, gdb on the ppc64 works fine, where as gdb on the ppc
fails to track threads.  It seems in thread_db_new_objfile, gdb always
falls through with TD_NOLIBTHREAD.

I've compiled the latest GDB for both boards, my newly compiled
version of gdb fails to track threads for both boards.  Thus, I now
have a functional and a broken gdb for the ppc64.  My original intent
was to step through gdb on both boards looking for the point of
failure.

I've compared with LD_DEBUG=files for both the broken gdb and the
working gdb on the ppc64, the same libs are loaded in both cases. The
libc being using in both cases is NPTL enabled.

What information could I provide that would allow someone to point me
towards the correct place to look for the point of failure?

 Much Thanks,
 -Billy


       reply	other threads:[~2005-11-06 18:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ba824fa10511061049l746105adg34641d3ca477f91a@mail.gmail.com>
2005-11-06 18:52 ` B Mullins [this message]
2005-11-06 19:26   ` Daniel Jacobowitz
2005-11-06 22:51     ` B Mullins
2005-11-06 23:18       ` Daniel Jacobowitz

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=ba824fa10511061052h3e3ee17cmc75a1b4d7a54cf3e@mail.gmail.com \
    --to=mul.web06@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