From: Pedro Alves <palves@redhat.com>
To: Luis Machado <lgustavo@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] [v2] Remove unneeded pattern matching in gdb.base/maint.exp
Date: Fri, 02 Dec 2016 19:10:00 -0000 [thread overview]
Message-ID: <5c2fbefb-ad9d-e141-d091-9cf6f33c72d9@redhat.com> (raw)
In-Reply-To: <1480705356-15200-1-git-send-email-lgustavo@codesourcery.com>
On 12/02/2016 07:02 PM, Luis Machado wrote:
> Thanks for clarifying the gdb_prompt situation. Updated patch attached.
>
> Btw, check-read1 did catch the problem with a couple failures. I didn't know
> about that one.
There's more about it in gdb/testsuite/README.
> This gets rid of more useless pattern matching cases in gdb.base/maint.exp.
>
> gdb/testsuite/ChangeLog:
>
> 2016-12-02 Luis Machado <lgustavo@codesourcery.com>
>
> * gdb.base/maint.exp: Use gdb_test instead of gdb_test_multiple when
> possible.
> Remove useless pattern-matching code.
OK.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-12-02 19:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 17:06 [PATCH] " Luis Machado
2016-12-02 17:30 ` Pedro Alves
2016-12-02 17:41 ` Luis Machado
2016-12-02 17:48 ` Pedro Alves
2016-12-02 19:02 ` [PATCH] [v2] " Luis Machado
2016-12-02 19:10 ` Pedro Alves [this message]
2016-12-02 19:37 ` Luis Machado
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=5c2fbefb-ad9d-e141-d091-9cf6f33c72d9@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.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