public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "infinity0 at pwned dot gg" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug rust/29272] New: regression: previously OK rust tests crash with SIGILL/SEGV/ABRT on Debian armhf Date: Tue, 21 Jun 2022 09:42:13 +0000 [thread overview] Message-ID: <bug-29272-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29272 Bug ID: 29272 Summary: regression: previously OK rust tests crash with SIGILL/SEGV/ABRT on Debian armhf Product: gdb Version: 11.2 Status: UNCONFIRMED Severity: normal Priority: P2 Component: rust Assignee: unassigned at sourceware dot org Reporter: infinity0 at pwned dot gg Target Milestone: --- Created attachment 14158 --> https://sourceware.org/bugzilla/attachment.cgi?id=14158&action=edit rustc debuginfo test sample #1 1. Compile the attached test file `rustc -g associated-types.rs`. 2. Run `gdb -x dbg.script ./associated-types`, dbg.script as follows: ~~~~ set charset UTF-8 show version add-auto-load-safe-path /home/infinity0/rustc/./src/etc set print pretty off directory /home/infinity0/rustc/./src/etc file /home/infinity0/rustc/build/armv7-unknown-linux-gnueabihf/test/debuginfo/associated-types.gdb/a set language rust break 'associated-types.rs':111 break 'associated-types.rs':118 break 'associated-types.rs':122 break 'associated-types.rs':130 break 'associated-types.rs':137 break 'associated-types.rs':140 run print arg continue print inferred print explicitly continue print arg continue print arg continue print a print b continue print a print b continue quit ~~~~ This works for all rustc versions (I was able to test 1.13 - 1.59) on gdb 10 but fails with SIGILL on gdb 11.2 armhf Debian. Other rustc debuginfo tests fail with other signals, SIGSEGV, SIGABRT, etc. More specific details here: https://github.com/rust-lang/rust/issues/96983 -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-06-21 9:42 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-21 9:42 infinity0 at pwned dot gg [this message] 2022-06-21 9:56 ` [Bug rust/29272] " infinity0 at pwned dot gg 2022-06-23 11:02 ` infinity0 at pwned dot gg 2022-06-23 11:10 ` infinity0 at pwned dot gg 2022-10-21 10:54 ` luis.machado at arm dot com 2022-10-21 10:54 ` luis.machado at arm dot com 2022-10-25 13:03 ` luis.machado at arm dot com 2022-10-31 10:16 ` luis.machado at arm dot com 2022-11-11 9:27 ` [Bug gdb/29272] " luis.machado at arm dot com 2022-11-11 12:47 ` cvs-commit at gcc dot gnu.org 2022-11-11 12:48 ` luis.machado at arm dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-29272-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).