Get desktop application:
View/edit binary Protocol Buffers messages
Carries information about code modules that are loaded into a process. See src/google_breakpad/processor/code_module.h
Next value: 8
Used in:
,The base address of this code module as it was loaded by the process.
The size of the code module.
The path or file name that the code module was loaded from.
An identifying string used to discriminate between multiple versions and builds of the same code module. This may contain a uuid, timestamp, version number, or any combination of this or other information, in an implementation-defined format.
The filename containing debugging information associated with the code module. If debugging information is stored in a file separate from the code module itself (as is the case when .pdb or .dSYM files are used), this will be different from code_file. If debugging information is stored in the code module itself (possibly prior to stripping), this will be the same as code_file.
An identifying string similar to code_identifier, but identifies a specific version and build of the associated debug file. This may be the same as code_identifier when the debug_file and code_file are identical or when the same identifier is used to identify distinct debug and code files.
A human-readable representation of the code module's version.
A proto representation of a process, in a fully-digested state. See src/google_breakpad/processor/process_state.h
Next value: 13
The time-date stamp of the original minidump (time_t format)
If there was an assertion that was hit, a textual representation of that assertion, possibly including the file and line at which it occurred.
The index of the thread that requested a dump be written in the threads vector. If a dump was produced as a result of a crash, this will point to the thread that crashed. If the dump was produced as by user code without crashing, and the dump contains extended Breakpad information, this will point to the thread that requested the dump.
Stacks for each thread (except possibly the exception handler thread) at the time of the crash.
The modules that were loaded into the process represented by the ProcessState.
A string identifying the operating system, such as "Windows NT", "Mac OS X", or "Linux". If the information is present in the dump but its value is unknown, this field will contain a numeric value. If the information is not present in the dump, this field will be empty.
A short form of the os string, using lowercase letters and no spaces, suitable for use in a filesystem. Possible values are "windows", "mac", and "linux". Empty if the information is not present in the dump or if the OS given by the dump is unknown. The values stored in this field should match those used by MinidumpSystemInfo::GetOS.
A string identifying the version of the operating system, such as "5.1.2600 Service Pack 2" or "10.4.8 8L2127". If the dump does not contain this information, this field will be empty.
A string identifying the basic CPU family, such as "x86" or "ppc". If this information is present in the dump but its value is unknown, this field will contain a numeric value. If the information is not present in the dump, this field will be empty. The values stored in this field should match those used by MinidumpSystemInfo::GetCPU.
A string further identifying the specific CPU, such as "GenuineIntel level 6 model 13 stepping 8". If the information is not present in the dump, or additional identifying information is not defined for the CPU family, this field will be empty.
The number of processors in the system. Will be greater than one for multi-core systems.
Used in:
The type of crash. OS- and possibly CPU- specific. For example, "EXCEPTION_ACCESS_VIOLATION" (Windows), "EXC_BAD_ACCESS / KERN_INVALID_ADDRESS" (Mac OS X), "SIGSEGV" (other Unix).
If crash_reason implicates memory, the memory address that caused the crash. For data access errors, this will be the data address that caused the fault. For code errors, this will be the address of the instruction that caused the fault.
Used in:
Stack for the given thread
Represents a single frame in a stack See src/google_breakpad/processor/code_module.h
Next value: 8
Used in:
The program counter location as an absolute virtual address. For the innermost called frame in a stack, this will be an exact program counter or instruction pointer value. For all other frames, this will be within the instruction that caused execution to branch to a called function, but may not necessarily point to the exact beginning of that instruction.
The module in which the instruction resides.
The function name, may be omitted if debug symbols are not available.
The start address of the function, may be omitted if debug symbols are not available.
The source file name, may be omitted if debug symbols are not available.
The (1-based) source line number, may be omitted if debug symbols are not available.
The start address of the source line, may be omitted if debug symbols are not available.