does rtems 5.1 support create a core dump file when accessing a invalid address or other fatal errors?

[smallphd at aliyun.com]

It is a good starting place to handle the crash problem. Especially the records could be packed to send to a host computer using TCP/IP.
One of the question for us is there is no network interface. But we have a flash disk. So we should modify the send flow using file system instead of network.
Moreover, we need expand the recorded data to get more information of the crash.



smallphd at aliyun.com
 
From: Sebastian Huber
Date: 2020-09-18 00:00
To: smallphd at aliyun.com; devel
Subject: Re: does rtems 5.1 support create a core dump file when accessing a invalid address or other fatal errors?
Hello,
 
On 15/09/2020 12:58, smallphd at aliyun.com wrote:
> I am developing applications in rtems 5.1. As we know, my application 
> and rtems kernel are both in the same address space.
> So if my application access an invalid address or encounter other 
> fatal errors, I want the kernel not just being hunging, but create a 
> core dump file.
> This file contains the whole contents of memory and I could use a 
> debuger to analyse the file to handle the bug.
> The question arise because I do not want always debug rtems in the bsp.
 
in addition to dumping the current state of the application, you can use 
the event recording to get a bit of the dynamic behaviour before the crash:
 
https://docs.rtems.org/branches/master/user/tracing/eventrecording.html
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20200918/41f12d93/attachment.html>