Messages in this thread | | | Date | Mon, 27 Mar 2017 16:45:42 +0200 | From | none <> | Subject | Getting 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 ?
| |