Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: sellcey@cavium.com, gdb@sourceware.org
Subject: Re: gdb / thread_db / multiple ABI question
Date: Mon, 10 Jul 2017 09:43:00 -0000	[thread overview]
Message-ID: <1f97046b-2ffd-b4ac-6626-412b75a54dd5@redhat.com> (raw)
In-Reply-To: <1499459428.13519.35.camel@cavium.com>

> OK, setting libthread-db-search-path and debug libthread-db got me
> a bit further.  I don't get any errors or warnings about not being
> able to find or load libthread_db.  It's still not reading everything
> correctly though:
> 
> (gdb) info threads
> Found 0 new threads in iteration 0.
>   Id   Target Id         Frame 
> * 3    Thread 0xf739ef70 (LWP 8660) 0x00400680 in doSomeThing ()
>   4    Thread 0xf69bf490 (LWP 8662) warning: Couldn't find general-purpose registers in core file.
> PC register is not available

Do you get that same warning without libthread_db?  It sounds more
like an issue on the gdb<->bfd side than on the libthread_db side
of things.  (Put a breakpoint on "warning".  I believe it comes from
corelow.c:get_core_register_section.)

Thanks,
Pedro Alves


  parent reply	other threads:[~2017-07-10  9:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-07 18:20 Steve Ellcey
2017-07-07 18:36 ` Pedro Alves
2017-07-07 20:30   ` Steve Ellcey
2017-07-10  7:39     ` Yao Qi
2017-07-10 16:58       ` Steve Ellcey
2017-07-10  8:29     ` Andreas Schwab
2017-07-10  9:43     ` Pedro Alves [this message]
2017-07-10 18:02       ` Steve Ellcey
2017-07-10 18:21         ` Pedro Alves
2017-07-10 19:45           ` Steve Ellcey
2017-07-11  8:38             ` Yao Qi
2017-07-10 21:22           ` Steve Ellcey

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=1f97046b-2ffd-b4ac-6626-412b75a54dd5@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=sellcey@cavium.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