From: Joel Brobecker <brobecker@gnat.com>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/testsuite] Workaround timeout in default.exp
Date: Fri, 21 May 2004 16:10:00 -0000 [thread overview]
Message-ID: <20040521161041.GL10684@gnat.com> (raw)
In-Reply-To: <vt21xlejmnh.fsf@zenia.home>
> Darn. This discussion sounded familiar; it turns out I had a patch
> for this written back in 2002 that I guess I never submitted. Here it
> is, adapted for the current sources; default.exp runs on AIX with this
> patch.
>
> (Your solution seems simpler.)
The comment was slightly misleading. In your patch, you did essentially
the same as what I did (avoid using gdb_test), except that I didn't
break the expected output into several chunks as you did. I am guessing
it was to be able to isolate the line containing the GDB prompt, but
maybe that was because you wanted this test to be powerful enough to
match the lines the test is looking for in any order?
In any case, I think Daniel found the real problem.
> Sun Feb 3 19:52:31 2002 Jim Blandy <jimb@seadog.cygnus.com>
>
> * gdb.base/default.exp: Distinguish the GDB prompt as it appears
> in "info set" and "show" output from the true prompt.
--
Joel
next prev parent reply other threads:[~2004-05-21 16:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 21:01 Joel Brobecker
2004-05-18 21:42 ` Daniel Jacobowitz
2004-05-20 1:48 ` Joel Brobecker
2004-05-20 2:27 ` Daniel Jacobowitz
2004-05-21 1:14 ` Joel Brobecker
2004-05-21 1:31 ` Daniel Jacobowitz
2004-05-21 1:43 ` Joel Brobecker
2004-05-21 6:58 ` Jim Blandy
2004-05-21 16:10 ` Joel Brobecker [this message]
[not found] ` <20040521160554.GK10684@gnat.com>
2004-05-21 16:36 ` Daniel Jacobowitz
2004-05-21 17:28 ` Joel Brobecker
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=20040521161041.GL10684@gnat.com \
--to=brobecker@gnat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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