Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [rfa] gdb.base/volatile.exp / varargs.exp: replace send_gdb with gdb_test
Date: Thu, 20 May 2010 18:04:00 -0000	[thread overview]
Message-ID: <4BF5793D.10305@vmware.com> (raw)
In-Reply-To: <20100520155010.GA3019@adacore.com>

Joel Brobecker wrote:
> For the record, Michael and I were discussing privately by email,
> and one of the things I wrote was that he should feel free to commit
> if he feels confident about his patches.  Since this can be relatively
> mechanical, this should be relatively safe, and we can deal with
> adjustments using followup patches...
> 
>> 2010-05-19  Michael Snyder  <msnyder@vmware.com>
>>
>> 	* gdb.base/varargs.exp: Replace send_gdb with gdb_test.
>> 	* gdb.base/volatile.exp: Replace send_gdb with gdb_test.
> 
> Some questions/suggestions...
> 
>> -send_gdb "set print sevenbit-strings\n" ; gdb_expect -re "$gdb_prompt $"
>> -send_gdb "set print address off\n" ; gdb_expect -re "$gdb_prompt $"
>> -send_gdb "set width 0\n" ; gdb_expect -re "$gdb_prompt $"
>> +gdb_test "set print sevenbit-strings" "" \
>> +    "set print sevenbit-strings; ${testfile}"
>> +gdb_test "set print address off" "" \
>> +    "set print address off; ${testfile}"
>> +gdb_test "set width 0" "" \
>> +    "set width 0; ${testfile}"
> 
> Just wondering why you added the "testfile" at the end of the test
> description?

I copied it from an existing test.  My guess is that it
uniquifies the output, which otherwise would be identical
for a bunch of tests.

 > It does not seem to serve any purpose, and so yo should
> be able to simplify the above using:
> 
>> +gdb_test "set print sevenbit-strings" ""
>> +gdb_test "set print address off" ""
>> +gdb_test "set width 0" ""

Checking....  it seems that we have instances of at least four
different styles for these three specific statements.  I will
try to homogenize them.



  parent reply	other threads:[~2010-05-20 18:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-19 20:54 Michael Snyder
2010-05-20 16:13 ` Joel Brobecker
2010-05-20 16:31   ` Pedro Alves
2010-05-20 16:42     ` Joel Brobecker
2010-05-20 16:47       ` Pedro Alves
2010-05-20 17:09         ` Joel Brobecker
2010-05-20 17:57           ` Pedro Alves
2010-05-20 18:08           ` Michael Snyder
2010-05-20 19:45             ` [commit/testsuite] lib/gdb.exp: New gdb_test_no_output function Joel Brobecker
2010-05-20 18:04   ` Michael Snyder [this message]
2010-05-20 18:40     ` [rfa] gdb.base/volatile.exp / varargs.exp: replace send_gdb with gdb_test Joel Brobecker

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=4BF5793D.10305@vmware.com \
    --to=msnyder@vmware.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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