From: Luis Machado <lgustavo@codesourcery.com>
To: Pedro Alves <palves@redhat.com>,
"'gdb-patches@sourceware.org'" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Harden gdb.base/bp-permanent.exp
Date: Tue, 14 Apr 2015 12:27:00 -0000 [thread overview]
Message-ID: <552D07AD.2070408@codesourcery.com> (raw)
In-Reply-To: <552D00DB.6090002@redhat.com>
On 04/14/2015 08:58 AM, Pedro Alves wrote:
> On 04/14/2015 12:45 PM, Luis Machado wrote:
>
>> for {set i 0} {$i < $count} {incr i} {
>> + set test "p /x addr_bp\[$i\] = buffer\[$i\]"
>> gdb_test_multiple "p /x addr_bp\[$i\] = buffer\[$i\]" $test {
>
> Might as well replace the same string in the gdb_test_multiple too:
>
> gdb_test_multiple $test $test {
>
> OK with that change.
I've pushed this with the suggested change.
prev parent reply other threads:[~2015-04-14 12:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 17:11 Luis Machado
2015-04-10 10:05 ` Pedro Alves
2015-04-10 14:03 ` Luis Machado
2015-04-13 17:51 ` Luis Machado
2015-04-14 11:31 ` Pedro Alves
2015-04-14 11:45 ` Luis Machado
2015-04-14 11:58 ` Pedro Alves
2015-04-14 12:27 ` Luis Machado [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=552D07AD.2070408@codesourcery.com \
--to=lgustavo@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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