Skip to content

Cygwin doesn't report correct backtrace on panic #140304

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.

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

Closed
Berrysoft opened this issue Apr 25, 2025 · 0 comments · Fixed by #140398
Closed

Cygwin doesn't report correct backtrace on panic #140304

Berrysoft opened this issue Apr 25, 2025 · 0 comments · Fixed by #140398
Labels
A-backtrace Area: Backtraces C-bug Category: This is a bug. O-cygwin Target: *-pc-cygwin T-libs Relevant to the library team, which will review and decide on the PR/issue.

Comments

@Berrysoft
Copy link
Contributor

Berrysoft commented Apr 25, 2025

The current backtrace-rs doesn't handle cygwin binaries correctly. I have created a PR: rust-lang/backtrace-rs#704 and have also asked on zulip. No one answered me, so I have to open an issue here:(

Current behavior (RUST_BACKTRACE = full):

stack backtrace:
   0:        0x100553090 - <unknown>
   1:        0x10046e693 - <unknown>
   2:        0x10046e455 - <unknown>
   3:        0x10069c574 - <unknown>
   4:        0x100679e2f - <unknown>
   5:        0x1004f8bf3 - <unknown>
   6:        0x10048f942 - <unknown>
   7:        0x10046e420 - <unknown>
   8:        0x10042ace8 - <unknown>
   9:        0x10042ab97 - <unknown>
  10:        0x10042c5bb - <unknown>
  11:        0x10042bd00 - <unknown>
  12:        0x10046ee69 - <unknown>
  13:        0x10042b8d9 - <unknown>
  14:        0x10068be87 - <unknown>
  15:        0x100401497 - <unknown>
  16:        0x10040180b - <unknown>
  17:        0x10040159e - <unknown>
  18:        0x100401571 - <unknown>
  19:        0x100459ac1 - <unknown>
  20:        0x10042b545 - <unknown>
  21:        0x10042cca8 - <unknown>
  22:        0x10042b274 - <unknown>
  23:        0x100510d9b - <unknown>
  24:        0x10046b153 - <unknown>
  25:        0x10042b472 - <unknown>
  26:        0x10042cca8 - <unknown>
  27:        0x10042b1bb - <unknown>
  28:        0x100510dc1 - <unknown>
  29:        0x10046b106 - <unknown>
  30:        0x10040155a - <unknown>
  31:        0x1004014df - <unknown>
  32:        0x1800484d1 - <unknown>
  33:        0x180045f33 - <unknown>
  34:        0x180045ff4 - <unknown>
  35:                0x0 - <unknown>
@Berrysoft Berrysoft added the C-bug Category: This is a bug. label Apr 25, 2025
@rustbot rustbot added the needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. label Apr 25, 2025
@jieyouxu jieyouxu added T-libs Relevant to the library team, which will review and decide on the PR/issue. O-cygwin Target: *-pc-cygwin A-backtrace Area: Backtraces and removed needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. labels Apr 25, 2025
@bors bors closed this as completed in 6e2c39b May 7, 2025
rust-timer added a commit to rust-lang-ci/rust that referenced this issue May 7, 2025
Rollup merge of rust-lang#140398 - Berrysoft:cygwin-backtrace, r=tgross35

Fix backtrace for cygwin

Closes rust-lang#140304

Depends on:
- [x] rust-lang/backtrace-rs#704

This PR could not be merged until the above PR is merged. I'll update the submodule then.

EDIT: submodule updated.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-backtrace Area: Backtraces C-bug Category: This is a bug. O-cygwin Target: *-pc-cygwin T-libs Relevant to the library team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants