* Re: [bug-libsigsegv] Re: sigsegv on s390 only giving start address of page in segv handler
[not found] <4D7FD266.8050108@redhat.com>
@ 2011-03-15 21:23 ` Bruno Haible
0 siblings, 0 replies; only message in thread
From: Bruno Haible @ 2011-03-15 21:23 UTC (permalink / raw)
To: linux-s390
Christian Borntraeger wrote:
> Can you give some insights about the other use cases? Userspace page faults can
> be handled just fine with the page address (I have done that for the s390x
> port of valgrind). Would a "works most of the time but might return the page
> address in 10% of the cases" be ok for your other use cases?
For most applications, that would work, yes. In GNU clisp, the fault handler
needs some changes, because it assumed to be able to detect the region
within the page based on the address, and had some related assertions. But
in the end, the mprotect() call emitted by the fault handler depends only on
the page and not on the address within the page.
Bruno
--
In memoriam Diego de Enzinas <http://en.wikipedia.org/wiki/Diego_de_Enzinas>
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2011-03-15 21:23 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <4D7FD266.8050108@redhat.com>
2011-03-15 21:23 ` [bug-libsigsegv] Re: sigsegv on s390 only giving start address of page in segv handler Bruno Haible
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.