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

Issue 258860043: Stack traces should have most significant entry first. (Closed)

Can't Edit
Can't Publish+Mail
Start Review
Created:
8 years, 9 months ago by egon
Modified:
8 years, 9 months ago
Reviewers:
nduca(google)
CC:
tracing-review_chromium.org
Base URL:
https://github.com/google/trace-viewer@master
Visibility:
Public.

Description

Stack traces should have most significant entry first. BUG=#753 R=nduca@google.com Committed: https://chromium.googlesource.com/external/trace-viewer/+/2fbfc17d36a30c2a6bd0e664843ce283b550771d

Patch Set 1 #

Total comments: 1

Patch Set 2 : Add docstring #

Unified diffs Side-by-side diffs Delta from patch set Stats (+17 lines, -15 lines) Patch
M tracing/tracing/extras/importer/trace_event_importer_test.html View 1 chunk +1 line, -1 line 0 comments Download
M tracing/tracing/extras/importer/v8/v8_log_importer_test.html View 3 chunks +12 lines, -12 lines 0 comments Download
M tracing/tracing/model/sample_test.html View 1 chunk +1 line, -1 line 0 comments Download
M tracing/tracing/model/stack_frame.html View 1 2 chunks +3 lines, -1 line 0 comments Download

Messages

Total messages: 3
egon
PTAL
8 years, 9 months ago (2015-07-19 16:38:53 UTC) #1
nduca(google)
lgtm in the long haul, i kinda suspect people will have religion about this and ...
8 years, 9 months ago (2015-07-21 17:55:27 UTC) #2
egon
8 years, 9 months ago (2015-07-21 18:13:40 UTC) #3
Message was sent while issue was closed.
Committed patchset #2 (id:20001) manually as
2fbfc17d36a30c2a6bd0e664843ce283b550771d (presubmit successful).
Sign in to reply to this message.

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