From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Fernando Nasser <fnasser@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [rfa/testsuite/mi] Fix transient failures in mi*-hack-cli.exp
Date: Sun, 14 Oct 2001 16:47:00 -0000 [thread overview]
Message-ID: <20011014194805.A5331@nevyn.them.org> (raw)
In-Reply-To: <3BCA222A.2050601@cygnus.com>
On Sun, Oct 14, 2001 at 07:39:22PM -0400, Andrew Cagney wrote:
> I wrote:
>
> >Um, I'd actually like to study this one in more detail
>
> Daniel wrote:
>
> >This one was a real nuisance to find...
> >
> >mi_gdb_test expects strings without the trailing newline. If there is a
> >trailing newline, we'll get two prompts back. In some cases, depending on
> >the delicacy of timing, this can cause a problem. The output looks like:
> >
> >47show architecture
> >
> >&"show architecture\n"
> >~"The target architecture is assumed to be i386\n"
> >47^done
> >(gdb)
> >&"\n"
> >^done
> >(gdb)
> >
> >Removing the unnecessary newlines masks the bug, as best as my tests can
> >tell. OK to commit?
>
> (sorry for the delay).
>
> More to the point, it shouldn't send the blank line anyway
> Yes, ok. I think 5.1 branch as well since a random pass/fail will
> confuse people trying to report test results.
OK, I'll do that on Monday. If no one objects (why would anyone
object? :) I'm going to put my other recent testsuite fixes on the
branch too; they fix timeout issues, and it's much more convenient to
run the testsuite after they're applied. Is that OK?
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2001-10-14 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-28 15:47 Daniel Jacobowitz
2001-10-01 7:57 ` Fernando Nasser
2001-10-01 8:33 ` Andrew Cagney
[not found] ` <3BCA222A.2050601@cygnus.com>
2001-10-14 16:47 ` Daniel Jacobowitz [this message]
2001-10-27 17:31 ` Daniel Jacobowitz
2001-10-28 10:01 ` Daniel Jacobowitz
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=20011014194805.A5331@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@cygnus.com \
--cc=fnasser@redhat.com \
--cc=gdb-patches@sources.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