Will this include enough information to know what type of access violation, the
thread, the faulting address, and the instruction address?
It is a fatal error and it is a set of standard ones so maybe the master list
can be extended.
Put yourself in the programmer's position. You want enough information to fix
it.
Sebastian Huber <sebastian.hu...@embedded-brains.de> wrote:
On 07/04/2013 04:40 AM, Hesham Moustafa wrote:
> Hi,
>
> What's the best way(s) to handle memory exceptions that result from memory
> access and permission violations ? for example, what should happen if an area
> of memory set to be read only and a thread tried to write data into this area
> ?
> Currently I am using it in debugging purpose to monitor exception handling and
> get some details, bit what should happen in practice ?
The systems should end up in an exception which should call
rtems_fatal(
RTEMS_FATAL_SOURCE_EXCEPTION,
(rtems_fatal_code) exception_frame_pointer
);
This is all a single address space operating system can do. The fatal
extensions can then deal with the error.
--
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.hu...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
rtems-devel mailing list
rtems-devel@rtems.org
http://www.rtems.org/mailman/listinfo/rtems-devel
_______________________________________________
rtems-devel mailing list
rtems-devel@rtems.org
http://www.rtems.org/mailman/listinfo/rtems-devel
