[Bug nptl/22153] New: setxid abort impossible to debug

["peter.zelezny at dektech dot com.au" <sourceware-bugzilla at sourceware dot org>]

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

            Bug ID: 22153
           Summary: setxid abort impossible to debug
           Product: glibc
           Version: unspecified
            Status: UNCONFIRMED
          Severity: minor
          Priority: P2
         Component: nptl
          Assignee: unassigned at sourceware dot org
          Reporter: peter.zelezny at dektech dot com.au
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---

Created attachment 10422
  --> https://sourceware.org/bugzilla/attachment.cgi?id=10422&action=edit
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?

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