From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Cc: Iain Sandoe <iain@sandoe.co.uk>
Subject: Re: [committed][gdb/testsuite] Fix unterminated string in gdb.objc/basicclass.exp
Date: Sun, 14 Jul 2019 11:27:00 -0000 [thread overview]
Message-ID: <73cf5aa3-6732-0e4e-c9bd-0377fa26537a@suse.de> (raw)
In-Reply-To: <20190714112401.GA2892@delia>
[ Fixed email address ]
On 14-07-19 13:24, Tom de Vries wrote:
> Hi,
>
> The test-case gdb.objc/basicclass.exp contains an unterminated string,
> introduced in refactoring commit fa43b1d7ca "after gdb_run_cmd, gdb_expect ->
> gdb_test_multiple/gdb_test".
>
> Fix the unterminated string.
>
> Committed to trunk.
>
> Thanks,
> - Tom
>
> [gdb/testsuite] Fix unterminated string in gdb.objc/basicclass.exp
>
> gdb/testsuite/ChangeLog:
>
> 2019-07-14 Tom de Vries <tdevries@suse.de>
>
> PR testsuite/24760
> * gdb.objc/basicclass.exp: Fix unterminated string.
>
> ---
> gdb/testsuite/gdb.objc/basicclass.exp | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gdb/testsuite/gdb.objc/basicclass.exp b/gdb/testsuite/gdb.objc/basicclass.exp
> index d88655afb5..43b93cdaf9 100644
> --- a/gdb/testsuite/gdb.objc/basicclass.exp
> +++ b/gdb/testsuite/gdb.objc/basicclass.exp
> @@ -119,7 +119,7 @@ gdb_test continue \
> # Test resetting breakpoints when re-running program
> #
> gdb_run_cmd
> -gdb_test "" "Breakpoint \[0-9\]+,.*main .*argc.*argv.* at .*$srcfile:.*" "resetting breakpoints when r
> +gdb_test "" "Breakpoint \[0-9\]+,.*main .*argc.*argv.* at .*$srcfile:.*" "resetting breakpoints when rerunning"
>
> #
> # Continue until breakpoint (test re-setting breakpoint)
>
prev parent reply other threads:[~2019-07-14 11:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-14 11:24 Tom de Vries
2019-07-14 11:27 ` Tom de Vries [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=73cf5aa3-6732-0e4e-c9bd-0377fa26537a@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=iain@sandoe.co.uk \
/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