Lines Matching full:minidump

51 // ExceptionHandler can write a minidump file when an exception occurs,
64 // use different minidump callbacks for different call sites.
66 // In either case, a callback function is called when a minidump is written,
67 // which receives the full path or file descriptor of the minidump.  The
68 // caller can collect and write additional application state to that minidump,
78   // a minidump.  |context| is the parameter supplied by the user as
82   // attempting to write a minidump.  If a FilterCallback returns false,
84   // writing a minidump, allowing another handler the opportunity to handle it.
87   // A callback function to run after the minidump has been written.
89   // minidump. |context| is the parameter supplied by the user as
91   // whether a minidump file was successfully written.
107   // In certain cases, a user may wish to handle the generation of the minidump
117   // Before writing a minidump, the optional |filter| callback will be called.
119   // minidump.  The minidump content will be written to the file path or file
122   // If install_handler is true, then a minidump will be written whenever
125   // If |server_fd| is valid, the minidump is generated out-of-process.  If it
151   // Writes a minidump immediately.  This can be used to capture the execution
155   // generated for each minidump.  The file path can be retrieved in the
161   // minidump is overwritten.
172   // Write a minidump of |child| immediately.  This can be used to
218   // to be copied to the minidump when a crash happens.