search

freaking1 / crashpad

Automatically exported from code.google.com/p/crashpad
0 stars 0 forks source link

Add the command line, environment, and more to minidump files #19

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
There’s some process-level information that we aren’t currently recording 
at all or recording as well as we should be in minidump files:

 - Command line (argv)
 - Environment (environ)
 - Parent process ID and name/command line. Possibly include the entire process ancestry.
 - timeval (microsecond-resolution) process start time, snapshot time, and CPU times. Currently, only 32-bit time_t with 1-second resolution is available.

The command line and environment normally show up in the main thread’s stack 
memory dump, but are not easily accessible without scanning. When the snapshot 
is taken, it’s fairly easy to get this information reliably, and it should be 
stored in a dedicated part of the minidump.

This list may continue to grow.

Original issue reported on code.google.com by mark@chromium.org on 25 Mar 2015 at 6:22

GoogleCodeExporter commented 8 years ago 
 - Working directory
 - Resource limits (ulimit) (POSIX)
 - Thread-specific errno (POSIX) (GetLastError() on Windows?): it may be easier to have a specific struct field for this rather than requiring someone to find the magic thread-local storage slot. On many systems, the main thread’s errno is not in TLS, which argues even more in favor of a specific field.

Original comment by mark@chromium.org on 26 Mar 2015 at 4:33

GoogleCodeExporter commented 8 years ago 
 - Root directory (in case of chroot)
 - Executable name (may be different from argv[0], should be the same as module 0 but there may have been an error determining modules)

Original comment by mark@chromium.org on 26 Mar 2015 at 6:51