Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [python][patch] Add GDB Parameters functionality
Date: Tue, 27 Apr 2010 03:09:00 -0000	[thread overview]
Message-ID: <m3y6g9k2va.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4BD60B0C.9090604@redhat.com> (Phil Muldoon's message of "Mon, 26 	Apr 2010 22:52:12 +0100")

>>>>> "Phil" == Phil Muldoon <pmuldoon@redhat.com> writes:

Phil> On 04/26/2010 10:45 PM, Tom Tromey wrote:
Phil> +gdb_test "set test-file-param None" "Argument required.*" 
>> 
>> I don't understand this test.  From my reading, test-file-param is a
>> filename parameter.  And, "None" is a valid file name.  So why would
>> this be expected to print an error message?

Phil> Oops it is bogus, should not be there.  I was experimenting with
Phil> setting None in GDB, but abandoned it.  I've removed it from the
Phil> testsuite.

Thanks.  The updated patch is ok provided the new .exp runs without any
fails.

Tom


      reply	other threads:[~2010-04-27  3:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26 13:19 Phil Muldoon
2010-04-26 17:56 ` Eli Zaretskii
2010-04-27 12:26   ` Phil Muldoon
2010-04-27 17:45     ` Eli Zaretskii
2010-04-27 19:25       ` Phil Muldoon
2010-04-27 19:36         ` Eli Zaretskii
2010-04-27 20:05           ` Phil Muldoon
2010-04-28  2:59             ` Eli Zaretskii
2010-04-28  6:28               ` Phil Muldoon
2010-04-28  9:18                 ` Phil Muldoon
2010-04-28 17:15                   ` Eli Zaretskii
2010-04-28 20:31                     ` Phil Muldoon
2010-04-29  3:06                       ` Eli Zaretskii
2010-04-29 16:13                         ` Phil Muldoon
2010-04-26 21:45 ` Tom Tromey
2010-04-26 21:52   ` Phil Muldoon
2010-04-27  3:09     ` Tom Tromey [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=m3y6g9k2va.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pmuldoon@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