From: Daniel Jacobowitz <drow@false.org>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [rfc] add ppc testcase to test fpscr
Date: Fri, 22 Aug 2008 02:47:00 -0000 [thread overview]
Message-ID: <20080822024659.GA12951@caradoc.them.org> (raw)
In-Reply-To: <1219362081.29526.2.camel@localhost.localdomain>
On Thu, Aug 21, 2008 at 08:41:21PM -0300, Thiago Jung Bauermann wrote:
> On Thu, 2008-08-21 at 19:31 -0400, Daniel Jacobowitz wrote:
> > > Also, this adds the function gdb_send_cmd to lib/gdb.exp. More than once
> > > I've wanted to send a commad to GDB and wait to get the prompt back
> > > (because send_gdb is too fast and can create racy testcases). This
> > > function scratches that itch.
> >
> > Isn't this just the same as gdb_test "command" "" "" ?
>
> Tried that, didn't work. Your command would check for:
>
> -re "\[\r\n\]*()\[\r\n\]+$gdb_prompt $"
>
> Which apparently is not good...
>
> I admit I didn't look that much into it.
I'd have to see more details - the example I gave is used all over the
testsuite. e.g. find.exp, restore.exp, setshow.exp.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-08-22 2:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 23:18 Thiago Jung Bauermann
2008-08-21 23:32 ` Daniel Jacobowitz
2008-08-21 23:42 ` Thiago Jung Bauermann
2008-08-22 2:47 ` Daniel Jacobowitz [this message]
2008-08-22 18:13 ` Thiago Jung Bauermann
2008-09-02 21:40 ` Joel Brobecker
2008-09-02 23:35 ` Thiago Jung Bauermann
2008-09-02 23:46 ` Daniel Jacobowitz
2008-09-02 21:55 ` Daniel Jacobowitz
2008-09-03 20:15 ` Thiago Jung Bauermann
2008-09-03 21:01 ` Daniel Jacobowitz
2008-09-04 1:26 ` Thiago Jung Bauermann
2008-09-05 0:12 ` Joel Brobecker
2008-09-05 3:38 ` Thiago Jung Bauermann
2008-09-05 14:00 ` Joel Brobecker
2008-09-05 19:30 ` Thiago Jung Bauermann
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=20080822024659.GA12951@caradoc.them.org \
--to=drow@false.org \
--cc=bauerman@br.ibm.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