Struct fidl_fuchsia_feedback::CrashReport
source · 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.
Implementations§
source§impl CrashReport
impl CrashReport
Trait Implementations§
source§impl Debug for CrashReport
impl Debug for CrashReport
source§impl Decodable for CrashReport
impl Decodable for CrashReport
source§fn decode(&mut self, decoder: &mut Decoder<'_>, offset: usize) -> Result<()>
fn decode(&mut self, decoder: &mut Decoder<'_>, offset: usize) -> Result<()>
self
.
Callers must ensure that offset
is a multiple of
Layout::inline_align
, and that decoder.buf
has room for reading
Layout::inline_size
bytes at offset
. Read moresource§impl Encodable for CrashReport
impl Encodable for CrashReport
source§fn encode(
&mut self,
encoder: &mut Encoder<'_, '_>,
offset: usize,
recursion_depth: usize
) -> Result<()>
fn encode( &mut self, encoder: &mut Encoder<'_, '_>, offset: usize, recursion_depth: usize ) -> Result<()>
Handle::INVALID
. Callers must ensure that offset
is a
multiple of Layout::inline_align
, and that encoder.buf
has room for
writing Layout::inline_size
bytes at offset
. Read moresource§impl Layout for CrashReport
impl Layout for 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
.§fn supports_simple_copy() -> boolwhere
Self: Sized,
fn supports_simple_copy() -> boolwhere Self: Sized,
source§impl PartialEq<CrashReport> for CrashReport
impl PartialEq<CrashReport> for CrashReport
source§fn eq(&self, other: &CrashReport) -> bool
fn eq(&self, other: &CrashReport) -> bool
self
and other
values to be equal, and is used
by ==
.impl StructuralPartialEq for CrashReport
impl TopLevel for CrashReport
Auto Trait Implementations§
impl RefUnwindSafe for CrashReport
impl Send for CrashReport
impl Sync for CrashReport
impl Unpin for CrashReport
impl UnwindSafe for CrashReport
Blanket Implementations§
source§impl<T> Instrument for T
impl<T> Instrument for T
source§fn instrument(self, span: Span) -> Instrumented<Self>
fn instrument(self, span: Span) -> Instrumented<Self>
source§fn in_current_span(self) -> Instrumented<Self>
fn in_current_span(self) -> Instrumented<Self>
§impl<T> LayoutObject for Twhere
T: Layout,
impl<T> LayoutObject for Twhere T: Layout,
§fn inline_align(&self, context: &Context) -> usize
fn inline_align(&self, context: &Context) -> usize
Layout::inline_align
.§fn inline_size(&self, context: &Context) -> usize
fn inline_size(&self, context: &Context) -> usize
Layout::inline_size
.