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 rust/30211] Crash on tab completing while debugging rust program
Date: Sat, 18 Mar 2023 15:32:46 +0000	[thread overview]
Message-ID: <bug-30211-4717-BIicAivaRu@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30211-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30211

--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
strncmp_iw_with_mode (grrrr) assumes that template stuff has to
come "later" in the symbol.  But in Rust, that's not really so.
The symbol in question is:

<&str as core::str::pattern::Pattern>::is_contained_in::hf6f1247c1a3fce69

gdb also incorrectly deduces:

(top-gdb) p symbol_language
$26 = language_cplus

... i.e., yet another issue caused by the _Z encoding ...

ultimately leading to a bad call to

                match_for_lcd->mark_ignored_range (template_start, string1);

Anyway this is a cluster of bad decisions, one by Rust, but more by gdb.

I suspect we might be able to fix this via bug #20367.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-03-18 15:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07 19:16 [Bug rust/30211] New: " sourceware at vorpal dot se
2023-03-07 19:17 ` [Bug rust/30211] " sourceware at vorpal dot se
2023-03-18 15:22 ` tromey at sourceware dot org
2023-03-18 15:32 ` tromey at sourceware dot org [this message]
2023-03-18 18:28 ` sourceware at vorpal dot se
2023-03-18 21:43 ` tromey at sourceware dot org
2023-03-19 15:23 ` tromey at sourceware dot org
2023-03-19 15:35 ` tromey at sourceware dot org
2023-03-20 13:53 ` cvs-commit at gcc dot gnu.org
2023-03-20 13:58 ` 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-30211-4717-BIicAivaRu@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).