Releases: rust-minidump/minidump-writer
Releases · rust-minidump/minidump-writer
0.10.1
Fixed
- PR#129 added checking of additions to ensure invalid memory offsets are gracefully handled.
- PR#135 resolved #134 by attempting to read the executables build id from the mapped file if it could not be retrieved from process memory.
- PR#136 changed to an older type to avoid requiring a semi-recent rust version.
0.10.0
Changed
- PR#118 resolved #72 by adding support for reading process memory via
process_vm_readv
and/proc/{pid}/mem
, in addition to the originalPTRACE_PEEKDATA
. This gives significant performance benefits as memory can now be read in blocks of arbitrary size instead of word-by-word with ptrace. - PR#128 and PR#133 updated the lockfile.
Fixed
- PR#127 resolved #27 by allowing programs to pass the needed auxv information, still falling back to reading
/proc/{pid}/auxv
to fill missing information, and being more permissive by still writing a dump if some or all of the auxv information could not be retrieved successfully rather than completely failing to write the minidump. - PR#131 resolved #124 by reinjecting non-
SIGSTOP
signals afterptrace::attach
so that the thread would be in the correct state afterptrace::detach
.
0.9.0
0.8.9
0.8.8
Fixed
- PR#108 resolved #28 by sending a
SIGSTOP
to the process that is about to be dumped to (hopefully) increase the robustness of the dumping process by reducing the chance of errors, particularly with regard to threads. This is done as a best effort, and will perform the old behavior if the process has not stopped within a timeout (by default 100ms), which can be overriden by the user.
0.8.7
0.8.6
Changed
- PR#104 slightly tweaked .so version parsing in the case of more "exotic" versions such as
libdbus-1.so.3.34.2rc5
. Previously this was parsed as3.34.25
but would cause ambiguity if there was ever an actual .25 patch/age in the future. Now, the last version is parsed as 1-2 numbers, ignoring non-digit characters if the last component has them. If 2 numbers are parsed, the last number is now placed in VS_FIXEDFILEINFO::product_version_lo so that it is distinct from the patch/age component placed in VS_FIXEDFILEINFO::product_version_hi.
0.8.5
Added
- PR#103 added
.so
file versions as additional metadata to minidumps, resolving this Mozilla bug. There is no true standard for .so file versions, so this is a best effort to pull what version information we can from the .so filename. The version components aremajor.minor.release
similarly to semver, wheremajor
-> VS_FIXEDFILEINFO::file_version_hi,major
-> VS_FIXEDFILEINFO::file_version_lo, andrelease
-> VS_FIXEDFILEINFO::product_version_hilibmozsandbox.so
->0.0.0
libstdc++.so.6.0.32
->6.0.32
libcairo-gobject.so.2.11800.0
->2.11800.0
libm.so.6
->6.0.0
libabsl_time_zone.so.20220623.0.0
->20220623.0.0
libdbus-1.so.3.34.2rc5
->3.34.25
Release 0.8.4
Release 0.8.3
Added
- PR#94 added support for writing file information for every file open in the process the dump is being performed for into the
MINIDUMP_HANDLE_DATA_STREAM
stream. - PR#90 added support for including the
/proc/<pid>/limits
file in theMozLinuxLimits
stream. This information can be used together with the file information described above to diagnose situations where the process was killed by the kernel due to file handle limits being hit. Thanks @lissyx!
Changed
- PR#94 updated several dependencies to align with
minidump-common
, which was also bumped.