public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/testsuite] Fix gdb.base/eh_return.exp
Date: Thu, 25 Jan 2024 07:50:17 -0700	[thread overview]
Message-ID: <87frylii1i.fsf@tromey.com> (raw)
In-Reply-To: <20240125110720.21486-1-tdevries@suse.de> (Tom de Vries's message of "Thu, 25 Jan 2024 12:07:20 +0100")

>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:

Tom> +gdb_expect {
Tom> +    -re "Breakpoint .*\r\n$gdb_prompt $" {
Tom> +	pass $test
Tom> +    }
Tom> +    -re "$inferior_exited_re normally.*\r\n$gdb_prompt $" {
Tom> +	unsupported $test
Tom> +    }
Tom> +    -re "\r\n$gdb_prompt $" {

I don't really know, but should these use -wrap instead of manually
matching the prompt regexp?

Tom

  reply	other threads:[~2024-01-25 14:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-25 11:07 Tom de Vries
2024-01-25 14:50 ` Tom Tromey [this message]
2024-01-25 14:53   ` Tom de Vries
2024-01-25 14:54     ` Tom Tromey
2024-01-25 15:27       ` Tom de Vries

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=87frylii1i.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    /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).