From: Duane Ellis <duane@duaneellis.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: Tim Newsome <tim@sifive.com>, gdb <gdb@sourceware.org>
Subject: Re: can target code change architecture setting?
Date: Tue, 11 Oct 2016 14:30:00 -0000 [thread overview]
Message-ID: <FA6120EE-A298-4B95-B037-C461A3443561@duaneellis.com> (raw)
In-Reply-To: <CAH=s-PMXhOcr5EhK0RShxqgurtV99NHvgBUOBWZocmkMttoCLg@mail.gmail.com>
>
>> Question #2 - How should the remote debugger respond to GDB?
>>
>> I don't think there is an "architecture change" packet.
>>
>
> Such packet is not needed, because GDB has to determine the gdbarch
> of each when unwinding.
I think you are making the assumption that GDB always has access to full debug (i.e.: dwarf) information.
In bare metal - You don’t always have this, you might have *labels* only (function name vrs address) but no source, no dwarf information.
The only solution is to *ask* the target “what is your *current* arch.
Or the target needs to send a “target-arch-change-indication” in some way.
-Duane.
next prev parent reply other threads:[~2016-10-11 14:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 16:48 duane
2016-10-10 19:46 ` Tim Newsome
2016-10-11 11:48 ` Yao Qi
2016-10-11 14:30 ` Duane Ellis [this message]
2016-11-03 19:47 ` Doug Evans
-- strict thread matches above, loose matches on Subject: below --
2016-10-07 17:38 Tim Newsome
2016-10-10 9:26 ` Yao Qi
2016-10-10 15:39 ` Tim Newsome
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=FA6120EE-A298-4B95-B037-C461A3443561@duaneellis.com \
--to=duane@duaneellis.com \
--cc=gdb@sourceware.org \
--cc=qiyaoltc@gmail.com \
--cc=tim@sifive.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