[Bug nptl/22153] setxid abort impossible to debug

["fweimer at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=22153

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fweimer at redhat dot com

--- Comment #1 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to peter.zelezny@dektech.com.au from comment #0)
> Created attachment 10422 [details]
> record 'error' into memory before abort()ing.
> 
> Hi,
> I recently got an abort() inside allocatestack.c::__nptl_setxid_error().
> Unfortunately it's impossible to see the last error from the syscall (from
> kernel). It would be really invaluable to see this number, but it tends to
> be optimized out into registers, which are then clobbered by abort() itself.
> 
> I suggest the newest 'error' is placed into the cmdp structure (into
> memory), so that core dumps will contain this value.
> 
> Would something like this (patch attached) be reasonable to do?

The patch looks reasonable.  Please post it to the mailing list.  Thanks.

-- 
You are receiving this mail because:
You are on the CC list for the bug.