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

Issue 205001: Refactor some X86 Stackwalker bits into parent classes (Closed)

Can't Edit
Can't Publish+Mail
Start Review
Created:
14 years, 1 month ago by Ted Mielczarek
Modified:
14 years, 1 month ago
Reviewers:
mochalatte, jimb
CC:
google-breakpad-dev_googlegroups.com
Visibility:
Public.

Description

I'm going to add stack scanning to the amd64 / arm stackwalkers, so this is some
refactoring to pull some bits that currently live on the X86 classes up to the
parent classes.

Patch Set 1 #

Total comments: 3
Unified diffs Side-by-side diffs Delta from patch set Stats Patch
M src/google_breakpad/processor/stack_frame.h View 2 chunks +19 lines, -1 line 0 comments Download
M src/google_breakpad/processor/stack_frame_cpu.h View 1 chunk +0 lines, -18 lines 0 comments Download
M src/google_breakpad/processor/stackwalker.h View 2 chunks +35 lines, -2 lines 1 comment Download
M src/processor/minidump_stackwalk.cc View 4 chunks +27 lines, -27 lines 1 comment Download
M src/processor/stackwalker_amd64.cc View 2 chunks +2 lines, -0 lines 0 comments Download
M src/processor/stackwalker_amd64_unittest.cc View 1 chunk +2 lines, -0 lines 1 comment Download
M src/processor/stackwalker_arm.cc View 2 chunks +2 lines, -0 lines 0 comments Download
M src/processor/stackwalker_arm_unittest.cc View 1 chunk +2 lines, -0 lines 0 comments Download
M src/processor/stackwalker_ppc.cc View 2 chunks +2 lines, -0 lines 0 comments Download
M src/processor/stackwalker_sparc.cc View 2 chunks +2 lines, -0 lines 0 comments Download
M src/processor/stackwalker_x86.cc View 8 chunks +9 lines, -32 lines 0 comments Download
M src/processor/stackwalker_x86.h View 1 chunk +0 lines, -13 lines 0 comments Download
M src/processor/stackwalker_x86_unittest.cc View 10 chunks +19 lines, -19 lines 0 comments Download

Messages

Total messages: 3
Ted Mielczarek
14 years, 1 month ago #1
jimb
LGTM! I love that moving the stack scanning function out to the base class and ...
14 years, 1 month ago #2
Ted Mielczarek
14 years, 1 month ago #3
On 2010/09/30 17:42:57, jimb wrote:
> http://breakpad.appspot.com/205001/diff/1/4
> File src/google_breakpad/processor/stackwalker.h (right):
> 
> http://breakpad.appspot.com/205001/diff/1/4#newcode120
> Line 120: template<typename instruction_type>
> Not sure, but I think type names that appear as template arguments should
follow
> the same naming conventions as other type names: StudlyCaps, no underscores.

Done.

> http://breakpad.appspot.com/205001/diff/1/5
> File src/processor/minidump_stackwalk.cc (right):
> 
> http://breakpad.appspot.com/205001/diff/1/5#newcode237
> Line 237: const char *trust_name;
> It might be nice to add a FrameTrustName static member function to the
> StackFrame base class to do this.

I added a non-static StackFrame::trust_description method. Seemed like a more
natural fit, although probably a bit odd since it's a struct.
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld 1004:630ec63f810e-tainted