0.8.9

Fixed

• PR#110 changed it so that SIGCONT is sent regardless if the process was not able to be SIGSTOPed quickly enough.
• PR#113 fixed a segfault(!) on linux if it was compiled with rustc 1.77.0 in release mode.

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

Changed

• PR#106 bumped minidump-common, minidump, minidump-processor, and minidump-unwind -> 0.21.

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 as 3.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 are major.minor.release similarly to semver, where major -> VS_FIXEDFILEINFO::file_version_hi, major -> VS_FIXEDFILEINFO::file_version_lo, and release -> VS_FIXEDFILEINFO::product_version_hi
  • libmozsandbox.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

Changed

• PR#97 bumped goblin -> 0.8.
• PR#99 bumped minidump-common -> 0.20, scroll -> 0.12, memmap2 -> 0.9.

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 the MozLinuxLimits 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.

Release 0.8.2

Added

• PR#86 added support for i686-android-linux.

Fixed

• PR#85 removed the dependency on chrono.
• PR#89 resolved #88 by merging ranges that were mapped, but had 1 or more unmapped ranges in between them.

Changed

• PR#87 updated some dependencies.

Release 0.8.1

Added

• PR#70 resolved #8 by adding support for writing MemoryInfoListStream on Linux/Android targets, this allows minidump consumers to process minidumps more easily without needing to parse and understand Linux-specific information. Thanks @afranchuk!
• PR#81 stabilized arm and aarch64 support for unknown-linux and linux-android, as well as adding support for x86_64-linux-android.

Changed

• PR#70 replaced the custom reading of procfs information used when generating a minidump on Linux to use the procfs crate instead, removing a bunch of code.
• PR#80 along with PR#84 replaced procfs with procfs-core, removing unneeded dependencies such as windows-sys.

Fixed

• PR#78 resolved #24 by ignoring guard pages when dumping the stack to the minidump in the event of a stack overflow.
• PR#83 resolved #82 by correctly aligning a structure.

Release 0.8.0

Removed

• PR#77 removed the dependency on winapi, all bindings are either part of minidump-writer or crash-context now.

Changed

• PR#77 closed #67 by allowing the user to specify the MinidumpType flags when creating a minidump.

Fixed

• PR#68 resolved #29 by ignoring the bening ESRCH error when detaching pthreads. Thanks @afranchuk!
• PR#74 resolved #73 by ensuring the NT_GNU_BUILD_ID section had the proper correct GNU name before using it as the build identifier.