public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Bruno Larsen <blarsen@redhat.com>
To: gdb-patches@sourceware.org
Cc: Bruno Larsen <blarsen@redhat.com>
Subject: [PATCH 0/2] Fix testing gdb.linespec/cp-completion-aliases with
Date: Tue, 17 Jan 2023 14:00:06 +0100	[thread overview]
Message-ID: <20230117130007.1686917-1-blarsen@redhat.com> (raw)

When running the test mentioned above with clang, I ran into the failure
explained in patch 2. To completely fix the testcase, however, I needed
to add a way to use regexes when expecting multiple complete
suggestions. That is what patch 1 does.

Bruno Larsen (2):
  gdb/testsuite: add test with regex for multiple completion patterns
  gdb/testsuite: fix running gdb.linespec/cp-completion-aliases.exp with
    clang

 .../gdb.linespec/cp-completion-aliases.exp    | 14 ++--
 gdb/testsuite/lib/completion-support.exp      | 73 +++++++++++++++----
 2 files changed, 67 insertions(+), 20 deletions(-)

-- 
2.39.0


             reply	other threads:[~2023-01-17 14:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17 13:00 Bruno Larsen [this message]
2023-01-17 13:00 ` [PATCH 1/2] gdb/testsuite: add test with regex for multiple completion patterns Bruno Larsen
2023-01-17 13:00 ` [PATCH 2/2] gdb/testsuite: fix running gdb.linespec/cp-completion-aliases.exp with clang Bruno Larsen
2023-02-03 13:44   ` Andrew Burgess
2023-02-03 15:49     ` Andrew Burgess
2023-02-06 14:10     ` Bruno Larsen
2023-02-06 15:48       ` Andrew Burgess
2023-02-03  8:04 ` [PING][PATCH 0/2] Fix testing gdb.linespec/cp-completion-aliases with Bruno Larsen

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=20230117130007.1686917-1-blarsen@redhat.com \
    --to=blarsen@redhat.com \
    --cc=gdb-patches@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).