Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: James-Adam Renquinha Henri <arenquinha@cimeq.qc.ca>
To: Fredrik Hederstierna <fredrik.hederstierna@verisure.com>,
	Yao Qi <qiyaoltc@gmail.com>,
	gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix exception unwinding for ARM Cortex-M
Date: Mon, 10 Jun 2019 21:25:00 -0000	[thread overview]
Message-ID: <cc501124-0248-2224-620c-02ab3eb2a7f8@cimeq.qc.ca> (raw)
In-Reply-To: <HE1PR1001MB130613C0995C4C21A630373BEF1B0@HE1PR1001MB1306.EURPRD10.PROD.OUTLOOK.COM>

Hi everyone in this thread, (not many as I see)

We could take another shot at integrating some changes to GDB so it 
works correctly, but that may only happen if there are the least amount 
of useless bike-shedding and that the right people in the mailing list 
contribute.

Basically, we must 1) make *very* clear the fact that Cortex-M devices 
are used typically in a bare-metal system with no OS (read: Linux) 
whatsoever, only possibly a tiny scheduler and that's all. That means we 
don't have to be concerned about "user visible" registers and whatnot, 
they are all visible anyway, and if the spec says that a register 
exists, *it is visible*, period. Other thing though, 2) my patch 
achieved its goal in a rather weaselly way, and the correct way is 
indeed to have it integrated into target features. But I need more info 
on the matter, and I'm a bit clueless about what to do with those 
"target features", how they are handled by GDB and how I can test the 
new configuration in isolation, without being "altered" by e.g. OpenOCD, 
which handily provides a target description that I can use as I did before.

I sure can figure it out all by myself, but that might be only after 
pouring an rather big amount of time into the matter that I cannot 
afford to do now. I need active collaboration and answers.

Here, let that message be in the mailing list for everyone to see.

James-Adam Renquinha Henri, Ing. jr
Ingénieur d'application
CIMEQ INC.


On 19-06-02 03 h 31, Fredrik Hederstierna wrote:
> Hi Yao, Adam,
> 
> 
> Some years back there was done some work done on unwinding on Cortex-M.
> 
> Only the very first start of the chain of patches was completed (new 
> function arm_m_pc_is_magic()).
> 
> 
> The actual real patch work with code work by me/Adam for cortex-M4F 
> MSP/PSP and unwinding did never reached the repo.
> 
> 
> What do you think of making another attempt to fix the stuff, I guess 
> all paper-work etc is in place, so we can try do a retake on this?
> 
> 
> Thanks, Best Regards, Fredrik
> 
> ------------------------------------------------------------------------
> *From:* Yao Qi <qiyaoltc@gmail.com>
> *Sent:* Tuesday, September 27, 2016 3:38 AM
> *To:* Adam Renquinha
> *Cc:* Fredrik Hederstierna; gdb-patches@sourceware.org
> *Subject:* Re: [PATCH] Fix exception unwinding for ARM Cortex-M
> On Mon, Sep 26, 2016 at 3:26 PM, Adam Renquinha <arenquinha@cimeq.qc.ca> 
> wrote:
>> That looks correct.
>>
> 
> Patch is pushed into master and 7.12.  The rest of your original
> patch is still welcome!
> 
> -- 
> Yao (齐尧)


       reply	other threads:[~2019-06-10 21:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AM4PR1001MB0948AC4D9CB635F5A9A2FC82EFDC0@AM4PR1001MB0948.EURPRD10.PROD.OUTLOOK.COM>
     [not found] ` <HE1PR1001MB130613C0995C4C21A630373BEF1B0@HE1PR1001MB1306.EURPRD10.PROD.OUTLOOK.COM>
2019-06-10 21:25   ` James-Adam Renquinha Henri [this message]
2019-06-12  9:01     ` Alan Hayward
2020-08-29  8:35       ` [PATCH] Fix exception stack " Fredrik Hederstierna
2020-09-02 13:24         ` Alan Hayward
2020-09-06  9:27           ` Fredrik Hederstierna
2020-09-09  8:12             ` Alan Hayward
2020-09-10 21:00               ` Fredrik Hederstierna
2020-09-14 14:44                 ` Alan Hayward
2020-09-14 18:31                   ` Joel Brobecker
2020-09-15 14:05                     ` Alan Hayward
2016-08-03 17:33 Re: [PATCH] Fix exception " James-Adam Renquinha Henri
     [not found] <OF625831A6.9C918507-ON00257FFE.0029D369-00257FFE.002D2551@notes.na.collabserv.com>
2016-07-29 11:47 ` Yao Qi
2016-08-02  9:43 ` Fredrik Hederstierna
2016-08-02 16:01   ` Yao Qi
2016-08-03 10:56   ` Fredrik Hederstierna
2016-08-03 11:19     ` Yao Qi
2016-08-04  7:04     ` Fredrik Hederstierna
2016-08-05 19:02       ` Adam Renquinha
2016-08-09  9:17         ` Yao Qi
2016-09-23 17:32           ` Adam Renquinha
2016-09-26  3:03             ` Yao Qi
2016-09-27  1:38               ` Adam Renquinha
2016-09-27  4:40                 ` Yao Qi

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=cc501124-0248-2224-620c-02ab3eb2a7f8@cimeq.qc.ca \
    --to=arenquinha@cimeq.qc.ca \
    --cc=fredrik.hederstierna@verisure.com \
    --cc=gdb-patches@sourceware.org \
    --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