diff options
| author | ivanpe@chromium.org <ivanpe@chromium.org> | 2014-11-25 22:45:23 +0000 |
|---|---|---|
| committer | ivanpe@chromium.org <ivanpe@chromium.org> | 2014-11-25 22:45:23 +0000 |
| commit | 63919583ba0d302a2ceb437ecf41a7975f44f54b (patch) | |
| tree | 41638178cfd8ae2637f3ebb4de31c5f49658029c /src/processor/proto | |
| parent | Introduce microdump_stackwalk comand line executable (diff) | |
| download | breakpad-63919583ba0d302a2ceb437ecf41a7975f44f54b.tar.xz | |
Surfacing the process create time in google_breakpad::ProcessState
and updating minidump_stackwalk to show process uptime.
I tested this with a minidump from Chrome and I got a result that
is inline with what the Windows debugger is showing for that dump:
minidump_stackwalk output:
--------------------------
Process uptime: 601 seconds
WinDBG output:
--------------
Process Uptime: 0 days 0:10:01.000
I didn't update the machine readable output of minidump_stackwalk
on purpose in order to avoid breaking someone that uses it.
It can be added later to the machine output if needed.
R=mark@chromium.org
Review URL: https://breakpad.appspot.com/7754002
git-svn-id: http://google-breakpad.googlecode.com/svn/trunk@1406 4c0a9323-5329-0410-9bdc-e9ce6186880e
Diffstat (limited to 'src/processor/proto')
| -rw-r--r-- | src/processor/proto/process_state.proto | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/src/processor/proto/process_state.proto b/src/processor/proto/process_state.proto index 5ff6194c..d3e02dc3 100644 --- a/src/processor/proto/process_state.proto +++ b/src/processor/proto/process_state.proto @@ -46,11 +46,14 @@ package google_breakpad; // A proto representation of a process, in a fully-digested state. // See src/google_breakpad/processor/process_state.h message ProcessStateProto { - // Next value: 13 + // Next value: 14 // The time-date stamp of the original minidump (time_t format) optional int64 time_date_stamp = 1; + // The time-date stamp when the process was created (time_t format) + optional int64 process_create_time = 13; + message Crash { // The type of crash. OS- and possibly CPU- specific. For example, // "EXCEPTION_ACCESS_VIOLATION" (Windows), "EXC_BAD_ACCESS / |