From: Bruno Larsen <blarsen@redhat.com>
To: Tom Tromey <tom@tromey.com>,
Bruno Larsen via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PING][PATCHv4] gdb/testsuite: modernize gdb.base/maint.exp
Date: Fri, 15 Jul 2022 14:20:33 -0300 [thread overview]
Message-ID: <c70147c5-b6eb-35b3-46a5-668028bb9426@redhat.com> (raw)
In-Reply-To: <87mtdapbhu.fsf@tromey.com>
On 7/15/22 13:49, Tom Tromey wrote:
>>> gdb.base/maint.exp was using several gdb_expect statements, probably
>>> because this test case predates the existance of gdb_test_multiple. This
>>> commit updates the test case to use gdb_test_multiple, making it more
>>> resilient to internal errors and such.
>>> The only gdb_expect left in the testcase is one that specifically
>>> looks
>>> for an internal error being triggered as a PASS.
>
> Thank you. I think this is ok.
thanks! Pushed
Cheers!
Bruno Larsen
>
> Tom
>
prev parent reply other threads:[~2022-07-15 17:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 18:04 [PATCH] " Bruno Larsen
2022-05-23 14:14 ` [PING] " Bruno Larsen
2022-05-30 11:14 ` [PINGv2] " Bruno Larsen
2022-06-06 12:43 ` [PINGv3] " Bruno Larsen
2022-06-13 20:03 ` [PINGv4] " Bruno Larsen
2022-06-20 13:29 ` [PINGv5] " Bruno Larsen
2022-06-21 15:52 ` Andrew Burgess
2022-06-21 19:45 ` Bruno Larsen
2022-06-21 19:54 ` [PATCHv2] " Bruno Larsen
2022-06-24 13:20 ` [PATCH] " Andrew Burgess
2022-06-24 15:13 ` Pedro Alves
2022-06-24 15:16 ` Pedro Alves
2022-06-24 15:23 ` Pedro Alves
2022-06-24 15:22 ` Pedro Alves
2022-06-24 17:51 ` Keith Seitz
2022-06-24 17:54 ` Bruno Larsen
2022-06-24 18:41 ` Pedro Alves
2022-06-27 10:13 ` Andrew Burgess
2022-06-28 18:36 ` [PATCHv3] " Bruno Larsen
2022-06-29 10:33 ` Andrew Burgess
2022-06-29 14:00 ` Bruno Larsen
2022-06-29 14:53 ` [PATCHv4] " Bruno Larsen
2022-07-13 11:22 ` [PING][PATCHv4] " Bruno Larsen
2022-07-15 16:49 ` Tom Tromey
2022-07-15 17:20 ` Bruno Larsen [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=c70147c5-b6eb-35b3-46a5-668028bb9426@redhat.com \
--to=blarsen@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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).