lkml.org 
[lkml]   [2017]   [Mar]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: Getting the way a SIGSEGV append when catching a SIGSEGV from within
On Mon, Mar 27, 2017 at 4:45 PM, none <ytrezq@sdf-eu.org> wrote:
> Hello,
>
> There’s three way to perform an invalid memory access :
>
> The attempt to execute/jump at an invalid address.
> The attempt to read at an invalid address.
> The attempt to write at an invalid address.
>
> Determining the execute case with rt_sigaction is easy : the last value of
> eip match the value of the address which caused the segfault.
>
> But how to know if the SIGSEGV occurred by a read or by a write attempt ? In
> the same time shouldn’t that information belong in the mmu ?

Did you look at the machine specific context of SIGSEGV?
It will give you access to the error code and the trap number.

--
Thanks,
//richard

\
 
 \ /
  Last update: 2017-03-27 17:33    [W:0.069 / U:0.600 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site