Lines Matching full:minidump

32 // programming errors.  If an exception occurs, a minidump file will be
71   // a minidump.  context is the parameter supplied by the user as
75   // attempting to write a minidump.  If a FilterCallback returns false, Breakpad
77   // minidump, allowing another handler the opportunity to handle it.
80   // A callback function to run after the minidump has been written.
81   // |minidump_id| is a unique id for the dump, so the minidump
84   // |succeeded| indicates whether a minidump file was successfully written.
93   // This bypasses the minidump file writing and simply gives the client
102   // Minidump files will be written to dump_path, and the optional callback
104   // If install_handler is true, then a minidump will be written whenever
114   // A special constructor if we want to bypass minidump writing and
122   // Get and set the minidump path.
130   // Writes a minidump immediately.  This can be used to capture the
150   // Write a minidump of child immediately. This can be used to capture
186   // All minidump writing goes through this one routine.
209   // path of the next minidump to be written in next_minidump_path_.
217   // The destination directory for the minidump
220   // The basename of the next minidump w/o extension
223   // The full path to the next minidump to be written, including extension
231   // The callback function and pointer to be passed back after the minidump
237   // The callback function to be passed back when we don't want a minidump
259   // Save the last result of the last minidump
262   // A mutex for use when writing out a minidump that was requested on a