Description[release-branch.go1.3] runtime: do not trace past jmpdefer during pprof traceback on arm
««« CL 107970043 / b336da131a84
runtime: do not trace past jmpdefer during pprof traceback on arm
jmpdefer modifies PC, SP, and LR, and not atomically,
so walking past jmpdefer will often end up in a state
where the three are not a consistent execution snapshot.
This was causing warning messages a few frames later
when the traceback realized it was confused, but given
the right memory it could easily crash instead.
Update issue 8153
LGTM=minux, iant
R=golang-codereviews, minux, iant
CC=golang-codereviews, r
https://codereview.appspot.com/107970043
»»»
Patch Set 1 #Patch Set 2 : diff -r bfc80b43b7ff https://code.google.com/p/go/ #Patch Set 3 : diff -r 3825729c6921 https://code.google.com/p/go/ #
MessagesTotal messages: 3
|