How memory access violation should be handled ?

[Peter Dufault]

On Jul 4, 2013, at 03:31 , Sebastian Huber <sebastian.huber at 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.
> 
> -- 

It would be useful to be able to get it into a signal handler using sigaction for SIGBUS or SIGSEGV. 

Peter
-----------------
Peter Dufault
HD Associates, Inc.      Software and System Engineering