From: Steve Ellcey <sellcey@cavium.com>
To: Pedro Alves <palves@redhat.com>, gdb@sourceware.org
Subject: Re: gdb / thread_db / multiple ABI question
Date: Fri, 07 Jul 2017 20:30:00 -0000 [thread overview]
Message-ID: <1499459428.13519.35.camel@cavium.com> (raw)
In-Reply-To: <306e2da9-4fea-76a2-e130-f6661f9826e8@redhat.com>
On Fri, 2017-07-07 at 19:36 +0100, Pedro Alves wrote:
>
> Though I have no idea whether an Aarch64 build of libthread_db is
> capable of biarch debugging.  It may be that GDB is already trying to
> the load the 64-bit libthread_db, but then libthread_db rejects
> the inferior for some reason.  The "set debug libthread-db" option
> should
> help you figure that out.  See below.
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
I don't see any code in gdb/linux-thread-db.c that seems to be
conditional on the word size (ILP32 vs LP64). Â I also don't see
anything in glibc nptl-db directory that appears to be conditional on
word size.  Things like pthread_t and __SIZEOF_PTHREAD_ATTR_T areÂ
different for the two different ABIs though. Â But that is true for x86
too and things seem to be working there. Â I am not sure what (if
anything) would need to be done to libthread_db to support biarch
debugging.
Steve Ellcey
sellcey@cavium.com
next prev parent reply other threads:[~2017-07-07 20:30 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 [this message]
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
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=1499459428.13519.35.camel@cavium.com \
--to=sellcey@cavium.com \
--cc=gdb@sourceware.org \
--cc=palves@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