lkml.org 
[lkml]   [2017]   [Mar]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectGetting the way a SIGSEGV append when catching a SIGSEGV from within
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 ?

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