[Bug tdep/28623] Missing catching return of execve syscall of PowerPC

["ulrich.weigand at de dot ibm.com" <sourceware-bugzilla@sourceware.org>]

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

--- Comment #5 from ulrich.weigand at de dot ibm.com ---
So if I get this correctly, the problem is that the execve syscall doesn't
really "return" as such, but rather starts execution at the entry point of the
new executable.  At this point, memory contents reflect the new executable and
register context are reset to the default setting on startup.

This means that you cannot reliably detect that you previously executed execve,
as that requires looking at memory and/or register contents (depending on
platform ABI details).  I guess your suggested patch(es) are heuristics to work
around that problem, but this seems somewhat fragile to me.

On the other hand, there is a reliable way to detect that we just executed an
execve syscall, and that is the TARGET_WAITKIND_EXECD wait state.  Maybe the
catch syscall logic, in the special case of catching execve, should somehow
hook into that event instead?

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