Re: How to get a stack trace in RTEMS

On 27.06.24 10:27, Stanislav Pankevich wrote: A small further update here to support the discussion further. It turns out that there is an undocumented function that, in contrast to _Unwind_Backtrace, allows passing a given stack: /    In my practice standard _Unwind_Backtrace failed to switch

Re: How to get a stack trace in RTEMS

A small further update here to support the discussion further. It turns out that there is an undocumented function that, in contrast to _Unwind_Backtrace, allows passing a given stack: *In my practice standard _Unwind_Backtrace failed to switch to pre-signal stack. I've managed to get some bef

Re: How to get a stack trace in RTEMS

Hi Sebastian, We had to add -funwind-tables to have this trace() called, and we can now see the function names as follows. The challenge is that the functions of the exception handler are printed, not the code that led to the exception. Now we need to figure out how to switch this code to print ou

Re: How to get a stack trace in RTEMS

Hello Stanislav, On 26.06.24 11:15, Stanislav Pankevich wrote: Dear RTEMS community, My colleague George cannot register to post to this forum, getting 403 when subscribing at https://lists.rtems.org/mailman/listinfo/users . I am posting this q

How to get a stack trace in RTEMS

Dear RTEMS community, My colleague George cannot register to post to this forum, getting 403 when subscribing at https://lists.rtems.org/mailman/listinfo/users. I am posting this question on his behalf. --- We are currently seeing an RTEMS_FATAL_SOURCE_EXCEPTION right at the start of execution a