does rtems 5.1 support create a core dump file when accessing a invalid address or other fatal errors?
gedare at rtems.org
Tue Sep 15 15:26:31 UTC 2020
No, there is no facility to generate a core dump. Due to shared
address space, once there is a fatal error you can't really trust
anything running in the target. You wouldn't necessarily want to try
writing to a mounted filesystem.
You could probably set up a debugger to do something like this by
triggering it in the fatal exception handler. You'd need to make use
of whatever the debugger can do already though. You really can't rely
on the executing target.
On Tue, Sep 15, 2020 at 4:58 AM smallphd at aliyun.com <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.
> smallphd at aliyun.com
> devel mailing list
> devel at rtems.org
More information about the devel