Getting the way a SIGSEGV append when catching a SIGSEGV from within

From	none <ytrezq@sdf-eu.org>
Newsgroups	linux.kernel
Subject	Getting the way a SIGSEGV append when catching a SIGSEGV from within
Date	2017-03-27 17:00 +0200
Message-ID	<tpEhH-17e-11@gated-at.bofh.it> (permalink)
Organization	linux.* mail to news gateway

Show all headers | View raw

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 ?

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Getting the way a SIGSEGV append when catching a SIGSEGV from within none <ytrezq@sdf-eu.org> - 2017-03-27 17:00 +0200
  Re: Getting the way a SIGSEGV append when catching a SIGSEGV from within Richard Weinberger <richard.weinberger@gmail.com> - 2017-03-27 17:40 +0200
    Re: Getting the way a SIGSEGV append when catching a SIGSEGV from  within none <ytrezq@sdf-eu.org> - 2017-03-27 21:00 +0200
      Re: Getting the way a SIGSEGV append when catching a SIGSEGV from  within Richard Weinberger <richard@nod.at> - 2017-03-27 21:30 +0200

csiph-web