From: Zheng Zhan Liang <linuxmaker@163.com>
To: gdb-patches@sourceware.org
Cc: Zheng Zhan <zzlossdev@163.com>
Subject: [PATCH] I'm debugging https://github.com/helix-editor/helix.git@63dcaae1b9083396fb3faaef9eaa2421f7e48fb9, which is a editor implemented with rust lang. When I type gdb command below: (gdb) b pars gdb dumped. I got: m_match = 0x7fffd8173cc7 "parse::h3bbecc5bbd82b347" m_ignored_ranges = { first = 0x7fffd8173cbb "<impl str>::parse::h3bbecc5bbd82b347", second = 0x7fffd8173cc5 "::parse::h3bbecc5bbd82b347" }
Date: Mon, 2 Jan 2023 20:43:34 +0800 [thread overview]
Message-ID: <20230102124334.120786-1-linuxmaker@163.com> (raw)
From: Zheng Zhan <zzlossdev@163.com>
---
gdb/completer.h | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/gdb/completer.h b/gdb/completer.h
index 8b4ad8ec4d4..b1faa1b2d71 100644
--- a/gdb/completer.h
+++ b/gdb/completer.h
@@ -163,8 +163,11 @@ class completion_match_for_lcd
const char *prev = m_match;
for (const auto &range : m_ignored_ranges)
{
- m_finished_storage.append (prev, range.first);
- prev = range.second;
+ if (prev < range.first)
+ {
+ m_finished_storage.append (prev, range.first);
+ prev = range.second;
+ }
}
m_finished_storage.append (prev);
--
2.38.1
next reply other threads:[~2023-01-02 12:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 12:43 Zheng Zhan Liang [this message]
2023-01-05 20:24 ` Tom Tromey
2023-01-06 3:01 ` linuxmaker
2023-01-06 15:53 ` Andrew Burgess
2023-01-07 8:58 ` Zheng
2023-01-12 19:06 ` Andrew Burgess
2023-01-13 5:24 ` Zheng
2023-01-13 14:46 ` Andrew Burgess
2023-03-20 13:56 ` Tom Tromey
2023-03-20 16:08 ` Andrew Burgess
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=20230102124334.120786-1-linuxmaker@163.com \
--to=linuxmaker@163.com \
--cc=gdb-patches@sourceware.org \
--cc=zzlossdev@163.com \
/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).