From: Steve Ellcey <sellcey@cavium.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: Pedro Alves <palves@redhat.com>, gdb@sourceware.org
Subject: Re: gdb / thread_db / multiple ABI question
Date: Mon, 10 Jul 2017 16:58:00 -0000 [thread overview]
Message-ID: <1499705887.13519.41.camel@cavium.com> (raw)
In-Reply-To: <86lgnw91w9.fsf@gmail.com>
On Mon, 2017-07-10 at 08:39 +0100, Yao Qi wrote:
> Steve Ellcey <sellcey@cavium.com> writes:
>
> >
> > 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
> Take a look at aarch64-linux-nat.c:ps_get_thread_area.  It calls
> aarch64_ps_get_thread_area.
>
> >
> > 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.
> AArch64 linux GDB is able to debug arm-linux 32-bit program.
OK, there are actually changes in this file where as part of the
earlier ILP32 work, we changed:
(gdbarch_bfd_arch_info (gdbarch)->bits_per_word == 32)
to
(gdbarch_bfd_arch_info(gdbarch)->arch == bfd_arch_arm)
But maybe, for ps_get_thread_area (and other places?) we need the
original test for word size and not the arch check.
Steve Ellcey
sellcey@cavium.com
next prev parent reply other threads:[~2017-07-10 16:58 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 [this message]
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=1499705887.13519.41.camel@cavium.com \
--to=sellcey@cavium.com \
--cc=gdb@sourceware.org \
--cc=palves@redhat.com \
--cc=qiyaoltc@gmail.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