[bug-libsigsegv] Re: sigsegv on s390 only giving start address of page in segv handler
Christian Borntraeger wrote:
> I even think that this cannot be fully solved by looking at the instruction,
> e.g. you cannot tell which access triggered the fault for instruction with
> two memory accesses (mvc) in the same page.
Sure you can. If it's a "read" fault (i.e. the page has no readable mapping),
you can claim the source address operand is the fault address. Otherwise,
i.e. if it's a "write" fault, the destination address operand is the fault