Update minidump requirement from 0.18 to 0.19

[dependabot[bot]]

Updates the requirements on minidump to permit the latest version.

Release notes

Sourced from minidump's releases.

Version 0.19.1 (2023-11-02)

Release Notes

• Fixed an issue that prevent the GitHub integration from automatically generating a new release.
• Updated all dependencies to address some mild security issues in some of the dependent crates.

Install minidump-stackwalk 0.19.1

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/rust-minidump/rust-minidump/releases/download/v0.19.1/minidump-stackwalk-installer.sh | sh

Download minidump-stackwalk 0.19.1

File	Platform	Checksum
minidump-stackwalk-aarch64-apple-darwin.tar.xz	macOS Apple Silicon	checksum
minidump-stackwalk-x86_64-apple-darwin.tar.xz	macOS Intel	checksum
minidump-stackwalk-x86_64-pc-windows-msvc.zip	Windows x64	checksum
minidump-stackwalk-x86_64-unknown-linux-gnu.tar.xz	Linux x64	checksum

Changelog

Sourced from minidump's changelog.

Version 0.19.1 (2023-11-02)

• Fixed an issue that prevent the GitHub integration from automatically generating a new release.
• Updated all dependencies to address some mild security issues in some of the dependent crates.

Version 0.19.0 (2023-11-02)

• The stackwalker can now lookup symbols using a module's code identifier if the debug identifier is missing. This is useful with Windows minidumps lacking debug identifiers (a condition that happens rather frequently when Windows is running out of memory at the time of minidump generation).
• Added a custom MozLinuxLimits stream that captures the contents of the /proc/<pid>/limits file of the affected process.
• Add support for the HandleDataStream stream type. This includes all public types that can appear in the stream.
• Remove support for the ThreadIdNameMapping annotation which is unused since we added support for the thread names stream.

Version 0.18.0 (2023-09-18)

• Add support for the MozMacosBootargsStream minidump stream which captures information holding macOS kernel boot arguments.
• Always use the code file for unwinding on Windows when using native debug information. Previously the stack walker could use the PDB file which does not contain unwinding information in 64-bit builds.
• Populate the process ID field on Linux, this displays the PID of the crashed process.
• Expose the MINIDUMP_MEMORY_INFO fields in the public API.
• Disable bit-flip detection on 64-bit ARM minidumps since it's prone to false positives.

Version 0.17.0 (2023-05-17)

• Stack-walking using native debug information was somewhat buggy, after more thorough testing it should be now on-par with breakpad symbol file-based stack-walking.

New minidump-unwind crate

The stack walking machinery has been extracted from the minidump-processor crate and put in a separate one. This crate has significantly less dependencies than the minidump-processor crate which makes it easier to vendor it in projects that only care about stack walking.

Guard-page detection

While analyzing a crash minidump-stackwalk will check if the crashing address

... (truncated)

Commits

• c3de84b chore: Release
• 46a9833 Updated the release notes for the next version
• f6de402 Remove the MSI installer
• aae3c27 Updated all the dependencies to address several mild security issues in some ...
• 3a60101 chore: Release
• e92bcec Updated cargo-dist to version 0.4.2
• ca0a97d Updated the release notes for the next version
• 8e7457c Bump the versions of the fuzzing crates
• 403e1c9 Update symbolic and memmap2, also get rid of crate versions that were yanked
• 2851131 Add support for the MINIDUMP_HANDLE_DATA_STREAM stream (#885)
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[changelog-app[bot]]

Generate changelog in changelog-dir>`changelog/@unreleased`</changelog-dir

What do the change types mean?

- `feature`: A new feature of the service. - `improvement`: An incremental improvement in the functionality or operation of the service. - `fix`: Remedies the incorrect behaviour of a component of the service in a backwards-compatible way. - `break`: Has the potential to break consumers of this service's API, inclusive of both Palantir services and external consumers of the service's API (e.g. customer-written software or integrations). - `deprecation`: Advertises the intention to remove service functionality without any change to the operation of the service itself. - `manualTask`: Requires the possibility of manual intervention (running a script, eyeballing configuration, performing database surgery, ...) at the time of upgrade for it to succeed. - `migration`: A fully automatic upgrade migration task with no engineer input required. _Note: only one type should be chosen._

How are new versions calculated?

- ❗The `break` and `manual task` changelog types will result in a major release! - 🐛 The `fix` changelog type will result in a minor release in most cases, and a patch release version for patch branches. This behaviour is configurable in autorelease. - ✨ All others will result in a minor version release.

Type

- [ ] Feature - [ ] Improvement - [ ] Fix - [ ] Break - [ ] Deprecation - [ ] Manual task - [ ] Migration

Description

Update minidump requirement from 0.18 to 0.19 **Check the box to generate changelog(s)** - [ ] Generate changelog entry

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.