Re: [PATCH] [20/20] x86: Print which shared library/executable faulted in segfault etc. messages

> > And printing the offset into a mapping also always allows to find the > > correct fault point in a library even with randomized mappings. Previously > > there was no way to actually find the correct code address inside > > the randomized mapping. > > > > Relies on earlier patch to shorten th

Re: [PATCH] [20/20] x86: Print which shared library/executable faulted in segfault etc. messages

* Andi Kleen <[EMAIL PROTECTED]> wrote: > They now look like > > hal-resmgr[13791]: segfault at 3c rip 2b9c8caec182 rsp 7fff1e825d30 > error 4 in libacl.so.1.1.0[2b9c8caea000+6000] > > This makes it easier to pinpoint bugs to specific libraries. yep, that's really useful. I think the patch n

Re: [PATCH] [20/20] x86: Print which shared library/executable faulted in segfault etc. messages

Andi Kleen a écrit : They now look like hal-resmgr[13791]: segfault at 3c rip 2b9c8caec182 rsp 7fff1e825d30 error 4 in libacl.so.1.1.0[2b9c8caea000+6000] This makes it easier to pinpoint bugs to specific libraries. And printing the offset into a mapping also always allows to find the correc

[PATCH] [20/20] x86: Print which shared library/executable faulted in segfault etc. messages

They now look like hal-resmgr[13791]: segfault at 3c rip 2b9c8caec182 rsp 7fff1e825d30 error 4 in libacl.so.1.1.0[2b9c8caea000+6000] This makes it easier to pinpoint bugs to specific libraries. And printing the offset into a mapping also always allows to find the correct fault point in a lib