You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dtrace: ensure ustack works regardless of glibc stack implementation
Older glibc versions were providing start code to be linked into executable
with a flawed implementation for setting up the initial frame. As a result,
the frame usually ended up with a frame pointer value pointing to the
beginning of the stack. Because this was the established implementation,
the ustack() implemented for aarch64 was based on this design.
Later glibc versions fix this mistake, and set up the initial frame with a
NULL frame pointer (as appears to be expected on aarch64).
The ustack() unwinder for aarch64 has been updated to handle both versions
of initial frames correctly.
Orabug: 29174561
Signed-off-by: Kris Van Hees <[email protected]>
Reviewed-by: Nick Alcock <[email protected]>
0 commit comments