Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] (long) sepdebug.exp replace send_gdb with gdb_test
Date: Thu, 20 May 2010 18:02:00 -0000	[thread overview]
Message-ID: <4BF5780A.2010600@vmware.com> (raw)
In-Reply-To: <201005201741.52364.pedro@codesourcery.com>

Pedro Alves wrote:
> I didn't to a thorough review, but I noticed a couple of
> issues.
> 
> On Thursday 20 May 2010 01:06:53, Michael Snyder wrote:
>> -# Test deleting all breakpoints when there are none installed,
>> -# GDB should not prompt for confirmation.
>> -# Note that gdb-init.exp provides a "delete_breakpoints" proc
>> -# for general use elsewhere.
>> -
>> -send_gdb "delete breakpoints\n"
>> -gdb_expect {
>> -     -re "Delete all breakpoints.*$" {
>> -           send_gdb "y\n"
>> -           gdb_expect {
>> -               -re "$gdb_prompt $" {
>> -                   fail "Delete all breakpoints when none (unexpected prompt)"
>> -               }
>> -               timeout { fail "Delete all breakpoints when none (timeout after unexpected prompt)" }
>> -           }
>> -       }
>> -     -re ".*$gdb_prompt $"       { pass "Delete all breakpoints when none" }
>> -    timeout                { fail "Delete all breakpoints when none (timeout)" }
>> -}
>> +delete_breakpoints
> 
> delete_breakpoints doesn't do what the test was doing before.
> Notice the comment..  Whether what is being tested or not has any
> value in this case, is another question, but it seems
> to have been just blindly copied from break.exp.  You could
> just delete it it seems.

It was copied from break.exp, and I figured as long as it was
tested there, it didn't need to be tested again here.



> 
>> -  -re "Catchpoint \[0-9\]* .fork..*$gdb_prompt $"
>> -          {pass $name}
>> -  -re "Catch of fork not yet implemented.*$gdb_prompt $"
>> -         {pass $name}
>> -  -re "$gdb_prompt $"
>> -          {fail $name}
>> -  timeout {fail "(timeout) $name"}
>> +gdb_test_multiple "catch fork" $name {
>> +    -re "Catchpoint \[0-9\]* .fork.*" {
>> +       pass $name
> 
> You should make sure to always consume the prompt with gdb_test_multiple,
> otherwise, it may be left in the input stream and confuse follow up tests.

Uh-oh, I didn't know that.  Thanks, I'll have to redo several of these.



  reply	other threads:[~2010-05-20 17:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-20  0:59 Michael Snyder
2010-05-20 16:47 ` Pedro Alves
2010-05-20 18:02   ` Michael Snyder [this message]
2010-05-20 18:15     ` Pedro Alves
2010-05-20 18:24       ` Michael Snyder

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=4BF5780A.2010600@vmware.com \
    --to=msnyder@vmware.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@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