Skip to content

Issues: rust-lang/rust

Draft release notes for 1.88.0
#141598 opened May 26, 2025 by Mark-Simulacrum
Open 9
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clear current search query, filters, and sorts
18 Open 5 Closed
18 Open 5 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Assigned to nobody Loading
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Panic backtrace on Arm64 Windows is truncated A-backtrace Area: Backtraces A-panic Area: Panicking machinery A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows C-bug Category: This is a bug. O-Arm Target: 32-bit Arm processors (armv6, armv7, thumb...), including 64-bit Arm in AArch32 state O-windows Operating system: Windows
#140489 opened Apr 29, 2025 by dpaoliello
@dpaoliello
3
Figure out how to make symbolisation code smaller A-backtrace Area: Backtraces C-enhancement Category: An issue proposing an enhancement or a PR with one. I-heavy Issue: Problems and improvements with respect to binary size of generated code. T-libs Relevant to the library team, which will review and decide on the PR/issue.
#139209 opened Apr 1, 2025 by joboet
10
-C force-frame-pointers=yes not respected by -Z build-std or opt-level = "z" A-backtrace Area: Backtraces A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#136198 opened Jan 28, 2025 by rslawson
14
Tracking Issue for short backtraces in the default panic hook A-backtrace Area: Backtraces A-debuginfo Area: Debugging information in compiled programs (DWARF, PDB, etc.) A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue.
#136129 opened Jan 27, 2025 by jyn514
8 tasks
Failed to capture backtrace when compiling with --remap-path-prefix=${PWD}= A-backtrace Area: Backtraces A-path-remapping Area: path remapping, --remap-path-prefix, --remap-cwd-prefix, --remap-diagnostics-scope etc. C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#135853 opened Jan 22, 2025 by ashi009
1
Infinite/long backtrace on i686 under Wine A-backtrace Area: Backtraces A-debuginfo Area: Debugging information in compiled programs (DWARF, PDB, etc.) A-panic Area: Panicking machinery A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows C-bug Category: This is a bug. E-needs-investigation Call for partcipation: This issues needs some investigation to determine current status O-windows Operating system: Windows O-x86_32 Target: x86 processors, 32 bit (like i686-*) (IA-32) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#135717 opened Jan 19, 2025 by purplesyringa
1
5
matching on functions with similar call stacks breaks optimized backtraces even with debuginfo A-backtrace Area: Backtraces A-debuginfo Area: Debugging information in compiled programs (DWARF, PDB, etc.) A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-discussion Category: Discussion or questions that doesn't represent real issues. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#134909 opened Dec 30, 2024 by jyn514
13
-musl platforms do not include unwind tables for libc A-backtrace Area: Backtraces C-bug Category: This is a bug. O-musl Target: The musl libc T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#134592 opened Dec 21, 2024 by RomanHargrave
2
shorten backtraces when called as a cdylib, not just for executables A-backtrace Area: Backtraces A-panic Area: Panicking machinery C-enhancement Category: An issue proposing an enhancement or a PR with one. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#134049 opened Dec 8, 2024 by jyn514
1
Write down where all the unwind/backtrace code is A-backtrace Area: Backtraces A-docs Area: Documentation for any part of the project, including the compiler, standard library, and tools A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows C-enhancement Category: An issue proposing an enhancement or a PR with one. E-tedious Call for participation: An issue involves lots of work and is better handled as many small tasks. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue.
#130257 opened Sep 12, 2024 by workingjubilee
1
Deadlock when capturing a backtrace from allocator during panic with test output capturing enabled A-backtrace Area: Backtraces A-libtest Area: `#[test]` / the `test` library C-bug Category: This is a bug. regression-from-stable-to-stable Performance or correctness regression from one stable version to another.
#130187 opened Sep 10, 2024 by Nemo157
2
RUST_BACKTRACE=full loop with -Cpanic=abort on aarch64-unknown-linux-gnu A-backtrace Area: Backtraces A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows C-bug Category: This is a bug. O-AArch64 Armv8-A or later processors in AArch64 mode P-high High priority regression-from-stable-to-stable Performance or correctness regression from one stable version to another. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#123733 opened Apr 10, 2024 by cuviper
1
25
Port backtrace-rs test-crates to rustc repo A-backtrace Area: Backtraces A-testsuite Area: The testsuite used to check the correctness of rustc C-bug Category: This is a bug. E-help-wanted Call for participation: Help is requested to fix this issue. E-mentor Call for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.
#122899 opened Mar 22, 2024 by workingjubilee
2 of 4 tasks
10
test ui/backtrace-debuginfo.rs is flaky A-backtrace Area: Backtraces A-debuginfo Area: Debugging information in compiled programs (DWARF, PDB, etc.) A-testsuite Area: The testsuite used to check the correctness of rustc C-bug Category: This is a bug. I-flaky-test Issue: A test is flaky/unreliable/spuriously fails O-windows-gnu Toolchain: GNU, Operating system: Windows O-x86_32 Target: x86 processors, 32 bit (like i686-*) (IA-32) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#117097 opened Oct 23, 2023 by ehuss
5
Tracking Issue for trim-paths RFC 3127 A-backtrace Area: Backtraces A-debuginfo Area: Debugging information in compiled programs (DWARF, PDB, etc.) A-reproducibility Area: Reproducible / deterministic builds B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC F-trim-paths Feature: trim-paths T-cargo Relevant to the cargo team, which will review and decide on the PR/issue. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#111540 opened May 13, 2023 by ehuss
2 of 12 tasks
35
tests/ui/panics/panic-short-backtrace-windows-x86_64.rs is disabled because of flakiness A-backtrace Area: Backtraces A-panic Area: Panicking machinery A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-bug Category: This is a bug. I-flaky-test Issue: A test is flaky/unreliable/spuriously fails O-windows Operating system: Windows O-windows-msvc Toolchain: MSVC, Operating system: Windows T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#92000 opened Dec 16, 2021 by matthiaskrgr
@wesleywiser
7
ICEs + RUST_BACKTRACE=1 should interleave the backtrace and query stack. A-backtrace Area: Backtraces A-diagnostics Area: Messages for errors, warnings, and lints A-query-system Area: The rustc query system (https://rustc-dev-guide.rust-lang.org/query.html) C-enhancement Category: An issue proposing an enhancement or a PR with one. D-diagnostic-infra Diagnostics: Issues that affect all diagnostics, or relate to the diagnostic machinery itself. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#70954 opened Apr 9, 2020 by eddyb
backtraces broken on the Android bot A-backtrace Area: Backtraces C-bug Category: This is a bug. O-android Operating system: Android T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#17520 opened Sep 24, 2014 by thestinger
1
27
ProTip! no:milestone will show everything without a milestone.