From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: Oleg Tolmatcev <oleg.tolmatcev@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v4] gdb: search local symbols before global symbols in completion
Date: Fri, 04 Sep 2026 12:03:14 -0600 [thread overview]
Message-ID: <87fqzo28t9.fsf@tromey.com> (raw)
In-Reply-To: <8733w7p9sg.fsf@tromey.com> (Tom Tromey's message of "Fri, 21 Aug 2026 13:12:47 -0600")
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
>>>>> "Oleg" == Oleg Tolmatcev <oleg.tolmatcev@gmail.com> writes:
Oleg> Still two regressions on ARM.
Tom> Here too:
Tom> FAIL: gdb.base/completion.exp: complete 'p values[0].a'
Tom> FAIL: gdb.base/completion.exp: complete 'p values[0] . a'
Tom> It's often better to just write a new small test case, at least in the
Tom> case when the otherwise-relevant test case is one of these old ones.
FWIW I wrote a test for the DAP completions request. It's pending on
the list. Anyway maybe it would not be difficult to modify that to
suit.
thanks,
Tom
prev parent reply other threads:[~2026-09-04 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-09 17:19 Oleg Tolmatcev
2026-08-10 18:00 ` Oleg Tolmatcev
2026-08-21 19:12 ` Tom Tromey
2026-09-04 18:03 ` Tom Tromey [this message]
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=87fqzo28t9.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=oleg.tolmatcev@gmail.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