Re: How to get caller stack information when crash happens?


Kinder, David B <david.b.kinder@...>
 

From: zephyr-devel-bounces@... [mailto:zephyr-devel-bounces@...] On Behalf Of Li, Jun R
Sent: Thursday, October 19, 2017 1:06 PM
To: Ilyes Gouta <ilyes.gouta@...>; Kumar Gala <kumar.gala@...>
Cc: zephyr-devel@...
Subject: Re: [Zephyr-devel] How to get caller stack information when crash happens?

 

Is there an issue to track this request? This feature is very useful for debugging.

 

Regards,

Jun

 

 

From: Ilyes Gouta <ilyes.gouta@...>
Date: Wednesday, October 18, 2017 at 11:06
To: Kumar Gala <kumar.gala@...>
Cc: "zephyr-devel@..." <zephyr-devel@...>, "Li, Jun R" <jun.r.li@...>
Subject: Re: [Zephyr-devel] How to get caller stack information when crash happens?

 

Hi,

 

On Oct 18, 2017 18:53, "Kumar Gala" <kumar.gala@...> wrote:


> On Oct 18, 2017, at 10:21 AM, Li, Jun R <jun.r.li@...> wrote:
>
> Hi,
> While I debug my application based on Zephyr, sometimes Fatal faults could happen on a specific thread, with the messages like below:
>
> shell> ***** BUS FAULT *****
>   Executing thread ID (thread): 0x20001814
>   Faulting instruction address:  0x800ed96
>   Precise data bus error
>   Address: 0x746e65d2
>   Imprecise data bus error
> Fatal fault in thread 0x20001814! Aborting.
>
>
> I’m wondering if there is any macro I can enable to get more information output, like caller stack list at the moment when the crash happens?
>
> Thank you!
>
> Jun Li
>

This is something we need to implement on the various arch’s.  Been wanting that myself.

 

A port of libunwind (https://savannah.nongnu.org/projects/libunwind/) to Zephyr might be a solution?

 

Ilyes

 


- k
_______________________________________________
Zephyr-devel mailing list
Zephyr-devel@...
https://lists.zephyrproject.org/mailman/listinfo/zephyr-devel

 

Join devel@lists.zephyrproject.org to automatically receive all group messages.