<div dir="ltr">Thanks,  I'll check it out.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Aug 19, 2020 at 1:53 PM Sebastian Huber <<a href="mailto:sebastian.huber@embedded-brains.de">sebastian.huber@embedded-brains.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 19/08/2020 10:15, Richi Dubey wrote:<br>
<br>
> Got it. Thanks for your answer. I'm working on your suggestion.<br>
<br>
As an addition to the use of GDB you can also use the event recording in <br>
combination with -finstrument-functions:<br>
<br>
<a href="https://docs.rtems.org/branches/master/user/tracing/eventrecording.html" rel="noreferrer" target="_blank">https://docs.rtems.org/branches/master/user/tracing/eventrecording.html</a><br>
<br>
You can use<br>
<br>
|#define CONFIGURE_RECORD_FATAL_DUMP_BASE64_ZLIB|<br>
<br>
|to dump the records in the fatal error handler. With the function <br>
instrumentation you get the sequence of function calls which resulted in <br>
the exception.<br>
|<br>
<br>
</blockquote></div>