On 20/04/2021 07:30, Chris Johns wrote:
We need a way for libdebugger or any other piece of software to capture and cascade the call. If this can be done on aarch64 then I am happy.
The fatal error extensions execute in a user controllable order. You can for example register a libdebugger handler which deals with break point exceptions before the signal mapping handler is called.
Synchronous exceptions should end up in an RTEMS_FATAL_SOURCE_EXCEPTION fatal error. The fatal code is a pointer to rtems_exception_frame (CPU_Exception_frame). In this data structure should be the complete state of the interrupted context (which could be also an interrupt handler). If you want to resume execution of the interrupted context, then we need an API for this (setters/getters and some sort of a longjmp()).
-- embedded brains GmbH Herr Sebastian HUBER Dornierstr. 4 82178 Puchheim Germany email: sebastian.hu...@embedded-brains.de phone: +49-89-18 94 741 - 16 fax: +49-89-18 94 741 - 08 Registergericht: Amtsgericht München Registernummer: HRB 157899 Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler Unsere Datenschutzerklärung finden Sie hier: https://embedded-brains.de/datenschutzerklaerung/ _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
