Releases: rust-minidump/minidump-writer
Releases · rust-minidump/minidump-writer
Release 0.8.2
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
andaarch64
support forunknown-linux
andlinux-android
, as well as adding support forx86_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
withprocfs-core
, removing unneeded dependencies such aswindows-sys
.
Fixed
Release 0.8.0
Removed
- PR#77 removed the dependency on
winapi
, all bindings are either part ofminidump-writer
orcrash-context
now.
Changed
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 correctGNU
name before using it as the build identifier.
Release 0.7.0
Release 0.6.0
Changed
- PR#60 removed the dependency on
windows-sys
due the massive version churn, resolving #58. This should allow projects to more easily integrate this crate into their project without introducing multiple versions of transitive dependencies. - PR#62 replaced
MDExceptionCodeLinux
withminidump_common::ExceptionCodeLinux
. - PR#64 updated dependencies.
Release 0.5.0
Changed
- PR#53 made the
mem_writer
anddir_section
modules public. Thanks @sage-msft! - PR#55 bumped
nix
,minidump-common
,minidump
,minidump-processor
anddump_syms
. Thanks
@sfackler! - PR#57 bumped
windows-sys
to 0.42.
Removed
- PR#56 removed the writing of the HandleOperationListStream stream, as it was essentially untested and was of dubious usefulness.
Release 0.4.0
Release 0.3.0
Fixed
- PR#42 resolved #41 by capping the VM read of task memory to avoid a syscall failure, as well as made it so that if an error does occur when reading the module's file path, the module is still written to the minidump, as the file path is less important than the UUID in terms of module identification.
- PR#44 resolved #43 by correctly calculating the base address of each loaded module. The bug was inherited from Breakpad.
- PR#44 and PR#45 resolved #37 by making the
crash_context::CrashContext
optional on MacOS and Windows, to make creating a minidump without necessarily having an actual crash more convenient for users.
Release 0.2.1
Release 0.2.0
Added
- PR#21 added an initial implementation for
x86_64-apple-darwin
andaarch64-apple-darwin