Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(992)

Issue 101260043: code review 101260043: [release-branch.go1.3] runtime: do not trace past jmpde... (Closed)

Can't Edit
Can't Publish+Mail
Start Review
Created:
9 years, 9 months ago by rsc
Modified:
9 years, 9 months ago
Reviewers:
r
CC:
golang-codereviews, r, adg, iant
Visibility:
Public.

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/ #

Unified diffs Side-by-side diffs Delta from patch set Stats (+17 lines, -0 lines) Patch
M src/pkg/runtime/asm_arm.s View 1 1 chunk +4 lines, -0 lines 0 comments Download
M src/pkg/runtime/traceback_arm.c View 1 1 chunk +13 lines, -0 lines 0 comments Download

Messages

Total messages: 3
rsc
Hello golang-codereviews@googlegroups.com (cc: adg, iant, r), I'd like you to review this change to https://code.google.com/p/go/
9 years, 9 months ago (2014-06-12 20:49:22 UTC) #1
r
LGTM
9 years, 9 months ago (2014-06-12 20:49:51 UTC) #2
rsc
9 years, 9 months ago (2014-06-12 20:55:34 UTC) #3
*** Submitted as https://code.google.com/p/go/source/detail?r=06752081de7d ***

[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
»»»

LGTM=r
R=golang-codereviews, r
CC=adg, golang-codereviews, iant
https://codereview.appspot.com/101260043
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b