Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1609957

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

Show all headers | View raw

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

Back to linux.kernel | Previous | Next — Previous in thread | 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