How memory access violation should be handled ?

Sebastian Huber sebastian.huber at
Thu Jul 4 13:27:58 UTC 2013

On 07/04/2013 03:19 PM, Joel Sherrill wrote:
> Will this include enough information to know what type of access violation, the thread, the faulting address, and the instruction address?

In case the source is RTEMS_FATAL_SOURCE_EXCEPTION the code is a pointer to 
rtems_exception_frame also known as CPU_Exception_frame.  So the information is 
CPU specific at the moment.

The thread is _Thread_Executing.

Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : sebastian.huber at
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.

More information about the devel mailing list