pub struct CrashReport {
pub program_name: Option<String>,
pub specific_report: Option<SpecificCrashReport>,
pub annotations: Option<Vec<Annotation>>,
pub attachments: Option<Vec<Attachment>>,
pub event_id: Option<String>,
pub program_uptime: Option<i64>,
pub crash_signature: Option<String>,
pub is_fatal: Option<bool>,
/* private fields */
}
Expand description
Represents a crash report.
Fields§
§program_name: Option<String>
The name of the program that crashed, e.g., the process or component’s name.
specific_report: Option<SpecificCrashReport>
The specific report that depends on the type of crashes.
This field should be set if additional information about the crashing program needs to be sent, e.g., a minidump.
annotations: Option<Vec<Annotation>>
A vector of key-value string pairs representing arbitrary data that should be attached to a crash report.
Keys should be unique as only the latest value for a given key in the vector will be considered.
attachments: Option<Vec<Attachment>>
A vector of key-value string-to-VMO pairs representing arbitrary data that should be attached to a crash report.
Keys should be unique as only the latest value for a given key in the vector will be considered.
event_id: Option<String>
A text ID that the crash server can use to group multiple crash reports related to the same event.
Unlike the crash signature, crash reports sharing the same ID correspond to different crashes, but can be considered as belonging to the same event, e.g., a crash in a low-level server causing a crash in a high-level UI widget.
program_uptime: Option<i64>
How long the program was running before it crashed.
crash_signature: Option<String>
A text signature that the crash server can use to track the same crash over time, e.g., “kernel-panic” or “oom”. This signature will take precedence over any automated signature derived from the rest of the data.
Unlike the event ID, crash reports sharing the same signature correspond to the same crash, but happening over multiple events, e.g., a null pointer exception in a server whenever asked the same request.
Must match [a-z][a-z-]* i.e. only lowercase letters and hyphens or this will result in a ZX_ERR_INVALID_ARGS epitaph.
is_fatal: Option<bool>
Indicates whether the crash report is for the atypical stop of a running process, component, or the system itself.
Examples of events that result in fatal crash reports are:
- an ELF process crashing
- the system rebooting because it ran out of memory.
- the system rebooting because a critical component crashed.
- the system rebooting because the device was too hot.
Examples of events that result in non-fatal crash reports are:
- an uncaught exception in a Dart program with many execution contexts. The runtime may chose to terminate that specific execution context and file a crash report for it instead of the whole program.
- a component detecting a fatal event (like an OOM) may occur soon, but isn’t guaranteed to occur.
This field is primarily used for grouping crashes by fatal, not fatal, and unknown, each corresponding to the field being set to true, set to false, or not set respectively.
Trait Implementations§
Source§impl Debug for CrashReport
impl Debug for CrashReport
Source§impl Decode<CrashReport, DefaultFuchsiaResourceDialect> for CrashReport
impl Decode<CrashReport, DefaultFuchsiaResourceDialect> for CrashReport
Source§fn new_empty() -> CrashReport
fn new_empty() -> CrashReport
Self
. The specific value does not matter,
since it will be overwritten by decode
.Source§impl Default for CrashReport
impl Default for CrashReport
Source§fn default() -> CrashReport
fn default() -> CrashReport
Source§impl Encode<CrashReport, DefaultFuchsiaResourceDialect> for &mut CrashReport
impl Encode<CrashReport, DefaultFuchsiaResourceDialect> for &mut CrashReport
Source§impl PartialEq for CrashReport
impl PartialEq for CrashReport
Source§impl ResourceTypeMarker for CrashReport
impl ResourceTypeMarker for CrashReport
Source§type Borrowed<'a> = &'a mut CrashReport
type Borrowed<'a> = &'a mut CrashReport
Encode<Self>
type cheaply obtainable from &mut Self::Owned
. There are three cases: Read moreSource§fn take_or_borrow<'a>(
value: &'a mut <CrashReport as TypeMarker>::Owned,
) -> <CrashReport as ResourceTypeMarker>::Borrowed<'a>
fn take_or_borrow<'a>( value: &'a mut <CrashReport as TypeMarker>::Owned, ) -> <CrashReport as ResourceTypeMarker>::Borrowed<'a>
&mut Self::Owned
to Self::Borrowed
. For
HandleBased
types this is “take” (it returns an owned handle and
replaces value
with Handle::invalid
), and for all other types it is
“borrow” (just converts from one reference to another).Source§impl TypeMarker for CrashReport
impl TypeMarker for CrashReport
Source§type Owned = CrashReport
type Owned = CrashReport
Source§fn inline_align(_context: Context) -> usize
fn inline_align(_context: Context) -> usize
Source§fn inline_size(_context: Context) -> usize
fn inline_size(_context: Context) -> usize
inline_align
.Source§fn encode_is_copy() -> bool
fn encode_is_copy() -> bool
Self::Owned
matches the FIDL wire
format and encoding requires no validation. When true, we can optimize
encoding arrays and vectors of Self::Owned
to a single memcpy. Read moreSource§fn decode_is_copy() -> bool
fn decode_is_copy() -> bool
Self::Owned
matches the FIDL wire
format and decoding requires no validation. When true, we can optimize
decoding arrays and vectors of Self::Owned
to a single memcpy.