Update Rust crate backtrace to 0.3.71 #1833
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
⚠ Artifact update problemRenovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: Cargo.lock |
|
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.3->0.3.71Release Notes
rust-lang/backtrace-rs (backtrace)
v0.3.71Compare Source
This is mostly CI changes, with a very mild bump to our effective cc crate version recorded, and a small modification to a previous changeset to allow backtrace to run at its current checked-in MSRV on Windows. Sorry about that! We will be getting 0.3.70 yanked shortly.
What's Changed
New Contributors
Full Changelog: rust-lang/backtrace-rs@0.3.70...0.3.71
v0.3.70Compare Source
New API
BacktraceFramecan now haveresolve(&mut self)called on it thanks to @fraillt in https://github.com/rust-lang/backtrace-rs/pull/526Platform Support
We added support for new platforms in this release!
Windows
thumbv7a-*-windows-msvctargets by @kleisauke in https://github.com/rust-lang/backtrace-rs/pull/573SGX
Thanks to
Internals
We did a bunch more work on our CI and internal cleanups
addr_of!by @GrigorenkoPV in https://github.com/rust-lang/backtrace-rs/pull/585symbolize/gimli/stash.rsby @onur-ozkan in https://github.com/rust-lang/backtrace-rs/pull/586New Contributors
Full Changelog: rust-lang/backtrace-rs@0.3.69...0.3.70
v0.3.69Compare Source
Thank you everyone for contributing to a very nice release!
Tracking Binary Size
As backtrace-rs is compiled into every single Rust program, we have begun tracking its binary size in order to find ways to reduce its impact on programs that only minimally use backtraces over time. This change is mostly relevant to this crate's CI, and has been implemented by @Kobzol and @detly over PRs #542, #544, #546, and #550!
Platform-Specific Fixes
As usual, the majority of PRs for this release only affect 1 or 2 platforms. Technically, even the binary-size tracking is only implemented to track binary size on
x86_64-unknown-linux-gnu.fuchsia
Backtraces for Fuchsia will now uses extended symbolization thanks to @liudangyi in https://github.com/rust-lang/backtrace-rs/pull/559
unix (with
procfs)Many Unix-y platforms support
/proc, including Linux and FreeBSD, but not OpenBSD. For those which do, backtrace uses/proc/self/mapsto assist in recovering the trace. We did not parse the output of/proc/self/mapsin a way that accounted for the fact that it may have spaces in path names, but this was fixed thanks to @MasonRemaley in https://github.com/rust-lang/backtrace-rs/pull/553windows-msvc
Some changes that should help binary size specifically on Windows MSVC targets, or at least compile times, have already been implemented, thanks to @klensy in https://github.com/rust-lang/backtrace-rs/pull/543 omitting compiling-in ELF backtrace capabilities. We don't have full binary size tracking for all major supported operating systems yet, so we believe this is worth 30KiB but that's more of an estimate than hard stats.
Dependency Management
New Contributors
Full Changelog: rust-lang/backtrace-rs@0.3.68...0.3.69
v0.3.68Compare Source
A bunch of behind-the-scenes work on upgrading CI has finally got things to a place where we can do confident releases again, so hopefully the next backtrace version will not take 6 months! Thanks to everyone who contributed to that! Most of the user-facing changes are about dependency updates and consequent improved platform compatibility, including with split DWARF. A few new functions on BacktraceFmt should also make it easier to inject additional text into backtrace's output.
New Contributors
Full Changelog: rust-lang/backtrace-rs@0.3.67...0.3.68
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.