public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug backtrace/29298] Internal error when debugging Rust programs
Date: Wed, 22 Mar 2023 16:10:52 +0000 [thread overview]
Message-ID: <bug-29298-4717-ZmiJU3Iduy@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29298-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29298
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #5 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Michael Schmidt from comment #4)
> I can reproduce this without setting demangle-style (rustc 1.67.0 (fc594f156
> 2023-01-24)), same conditions as with Nils. I bisected gdb and it seems this
> was introduced in 7f4307436f.
Maybe this is a dup of bug#30158 then.
Can you try a gdb from git, either from the 13 branch or from master?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-03-22 16:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 14:10 [Bug backtrace/29298] New: " nils at os dot inf.tu-dresden.de
2022-07-06 16:07 ` [Bug backtrace/29298] " tromey at sourceware dot org
2022-07-06 18:15 ` nils at os dot inf.tu-dresden.de
2022-08-05 14:29 ` tromey at sourceware dot org
2023-03-22 10:51 ` e11911636 at student dot tuwien.ac.at
2023-03-22 16:10 ` tromey at sourceware dot org [this message]
2023-03-22 16:46 ` e11911636 at student dot tuwien.ac.at
2023-03-22 20:30 ` tromey at sourceware dot org
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-29298-4717-ZmiJU3Iduy@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: link
Be 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).