From: Jim Blandy <jimb@red-bean.com>
To: fnf@specifix.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix problem with scope.exp test, skipping past init0 call
Date: Mon, 13 Feb 2006 06:16:00 -0000 [thread overview]
Message-ID: <8f2776cb0602122216m7ad00735i87f90be6b128465c@mail.gmail.com> (raw)
In-Reply-To: <200602121510.01657.fnf@specifix.com>
On 2/12/06, Fred Fish <fnf@specifix.com> wrote:
> 2006-02-12 Fred Fish <fnf@specifix.com>
>
> * gdb.base/scope.exp (test_at_main): Use gdb_test_multiple
> to handle cases where it takes two "next" commands to skip
> past the init call.
Looks good to me.
next prev parent reply other threads:[~2006-02-13 6:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-12 20:10 Fred Fish
2006-02-13 6:16 ` Jim Blandy [this message]
2006-02-13 15:39 ` Daniel Jacobowitz
2006-02-13 15:47 ` Fred Fish
2006-02-13 15:53 ` Daniel Jacobowitz
2006-02-13 16:05 ` Mark Kettenis
2006-02-13 16:08 ` Daniel Jacobowitz
2006-02-13 16:19 ` Fred Fish
2006-02-13 16:49 ` Mark Kettenis
2006-02-13 17:47 ` Jim Blandy
2006-02-13 17:54 ` Jim Blandy
2006-02-13 17:57 ` Jim Blandy
2006-02-13 18:08 ` Mark Kettenis
2006-03-02 0:01 ` Michael Snyder
2006-03-02 6:09 ` Jim Blandy
2006-02-13 18:39 ` Fred Fish
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=8f2776cb0602122216m7ad00735i87f90be6b128465c@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=fnf@specifix.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