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

Issue 31001: Added ability for crash_report to run through a directory

Can't Edit
Can't Publish+Mail
Start Review
Created:
15 years ago by krisr
Modified:
15 years ago
Reviewers:
mochalatte
CC:
google-breakpad-dev_googlegroups.com
Base URL:
http://google-breakpad.googlecode.com/svn/trunk/
Visibility:
Public.

Patch Set 1 #

Patch Set 2 : Fixing whitespace #

Patch Set 3 : More whitespace fixes #

Patch Set 4 : fixing while loop #

Patch Set 5 : adding neal as a reviewer #

Total comments: 1

Patch Set 6 : adding nealsid's suggestions #

Unified diffs Side-by-side diffs Delta from patch set Stats Patch
M src/tools/mac/crash_report/crash_report.mm View 1 2 3 4 5 2 chunks +28 lines, -5 lines 0 comments Download

Messages

Total messages: 1
mochalatte
15 years ago #1
LGTM, Kris
Thanks for the patch.

Neal

http://breakpad.appspot.com/31001/diff/1006/8
File src/tools/mac/crash_report/crash_report.mm (right):

http://breakpad.appspot.com/31001/diff/1006/8#newcode316
Line 316: && is_dir) {
i would just make this:

BOOL file_exists = [manager fileExistsAtPath:minidump_path isDirectory:is_dir];
if (file_exists && is_dir) { ...
...
} else if (file_exists) {
...

}
That way we're not potentially calling ProcessSingleReport on a nonexistant
file.(and it also gets away from a style of setting a variable and testing it in
the same boolean expression, which works but I'm not a fan of because it's
slightly harder to follow)
Sign in to reply to this message.

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