From: Yao Qi <qiyaoltc@gmail.com>
To: sellcey@cavium.com
Cc: Pedro Alves <palves@redhat.com>, gdb@sourceware.org
Subject: Re: gdb / thread_db / multiple ABI question
Date: Tue, 11 Jul 2017 08:38:00 -0000 [thread overview]
Message-ID: <86fue3qsfk.fsf@gmail.com> (raw)
In-Reply-To: <1499715948.13519.49.camel@cavium.com> (Steve Ellcey's message of "Mon, 10 Jul 2017 12:45:48 -0700")
Steve Ellcey <sellcey@cavium.com> writes:
> seem related to the ILP32 work. If I look at the note->type
> values that come in and get used in the switch statement, I see 0x401,
> 0x402, 0x403, and 0x404. But 0x404 is not defined
> in include/elf/common.h. There is a 0x405, but no 0x404. Any
> idea why?
0x404 is NT_ARM_SYSTEM_CALL, defined in kernel include/uapi/linux/elf.h.
--
Yao (齐尧)
next prev parent reply other threads:[~2017-07-11 8:38 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
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 [this message]
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=86fue3qsfk.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=gdb@sourceware.org \
--cc=palves@redhat.com \
--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