[PATCH] Save final 'error' in __nptl_setxid_error()

Peter Zelezny peter.zelezny@dektech.com.au
Tue Sep 19 07:55:00 GMT 2017


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?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: glibc-setxid-saveerror.patch
Type: text/x-patch
Size: 573 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20170919/04e84007/attachment.bin>


More information about the Libc-alpha mailing list