Releases: rust-minidump/minidump-writer
Releases · rust-minidump/minidump-writer
0.12.0
Changed
- PR#169 updated the crate to edition 2024 and an MSRV of 1.85.0.
- PR#172 updated dependencies, resolving several audit failures. The MSRV was changed to 1.88.0 due to the
timecrate. - PR#173 replaced the
windows-sysdependency introduced in PR#168 with inline bindings.
Fixed
Added
- PR#168 resolved MOZ#1831094 by adding functionality for reading process and module reading for each platform minidump-writer targets.
0.11.0
0.10.2
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_readvand/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}/auxvto 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-
SIGSTOPsignals afterptrace::attachso 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
SIGSTOPto 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.25but 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.