From: Tristan Gingold <gingold@adacore.com>
To: Christopher Friedt <chrisfriedt@gmail.com>
Cc: Pedro Alves <palves@redhat.com>, Yao Qi <qiyaoltc@gmail.com>,
gdb-patches@sourceware.org
Subject: Re: cortex-m xml register descriptions for m-system
Date: Thu, 17 Dec 2015 08:32:00 -0000 [thread overview]
Message-ID: <B54C5969-38AB-470D-ACF1-BD92EC5E4E93@adacore.com> (raw)
In-Reply-To: <CAF4BF-RhPPpW3FhXadbGqxafxmLyyHAwGPokpupnUZqVucYyfw@mail.gmail.com>
> On 16 Dec 2015, at 18:12, Christopher Friedt <chrisfriedt@gmail.com> wrote:
>
> On Wed, Dec 16, 2015 at 8:51 AM, Tristan Gingold <gingold@adacore.com> wrote:
>>
>>> On 15 Dec 2015, at 16:35, Christopher Friedt <chrisfriedt@gmail.com> wrote:
>>>
>>> Just so we can have consensus, please indicate what you think is the
>>> best solution - Pedro, Yao, & Tristan.
>>>
>>> Based on Tristan's feedback as well, it confirms that these registers
>>> are necessary for DWARF handling.
>>
>> Not sure about that. To my understanding, DWARF doesn’t need to refer
>> to psp or msp.
>
> Wait... just yesterday you wrote:
>
> "I do think so too.
>
> I have just written a patch so that gdb unwinds correctly on cortex-m
> exceptions, and this of course requires that gdb knows about at least
> psp."
>
> Maybe I'm confused. I presumed DWARF was involved in unwinding to some
> extent, but if its purely just used for debugging, it might not
> require PSP / MSP at all.
No, for unwinding through HW exceptions, dwarf is not used and couldn’t
be use: there is no code at the return addresses.
PSP is required because that can be previous stack before the exception.
> In any case PSP / MSP are most definitely used in unwinding.
I think that only PSP and SP are required (of course SP could be MSP).
Tristan.
next prev parent reply other threads:[~2015-12-17 8:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 17:05 Christopher Friedt
2015-12-14 18:55 ` Pedro Alves
2015-12-14 23:11 ` Christopher Friedt
2015-12-15 0:13 ` Pedro Alves
2015-12-15 15:35 ` Christopher Friedt
2015-12-16 13:51 ` Tristan Gingold
2015-12-16 17:13 ` Christopher Friedt
2015-12-17 8:32 ` Tristan Gingold [this message]
2018-08-14 18:14 ` Christopher Friedt
2015-12-15 11:44 ` Tristan Gingold
2015-12-15 11:59 ` Pedro Alves
2015-12-15 12:11 ` Pedro Alves
2015-12-15 12:13 ` Pedro Alves
2015-12-15 8:55 ` Yao Qi
2015-12-15 10:25 ` Pedro Alves
2015-12-15 10:32 ` Pedro Alves
2015-12-16 9:49 ` Yao Qi
2015-12-15 9:13 ` Yao Qi
2015-12-15 12:20 ` Christopher Friedt
2015-12-15 15:09 ` Christopher Friedt
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=B54C5969-38AB-470D-ACF1-BD92EC5E4E93@adacore.com \
--to=gingold@adacore.com \
--cc=chrisfriedt@gmail.com \
--cc=gdb-patches@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