From: Michael Chastain <mec.gnu@mindspring.com>
To: jmolenda@apple.com, gdb-patches@sources.redhat.com
Cc: cagney@gnu.org
Subject: Re: RFA: if/while commands in user-defined command behave differently
Date: Thu, 09 Sep 2004 14:34:00 -0000 [thread overview]
Message-ID: <414069F8.nailE691CTVHR@mindspring.com> (raw)
In-Reply-To: <76449857-01CD-11D9-9838-000A9569836A@apple.com>
send_gdb / gdb_expect are old; can you can upgrade this to the modern
interface, gdb_test_multiple? With gdb_test_multiple you don't need
the default "$gdb_prompt $" and timeout clauses.
The idea is good; it just needs gdb_test_multiple. Just do that and
re-test and re-submit.
Michael
===
[gdb/testsuite/ChangeLog]
2004-09-08 Jason Molenda (jmolenda@apple.com)
* gdb.base/define.exp: Two new tests to verify zero space chars
after 'if' and 'while' commands in a user-defined command is correctly
parsed.
next prev parent reply other threads:[~2004-09-09 14:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 19:30 Jason Molenda
2004-09-09 14:34 ` Michael Chastain [this message]
2004-09-10 0:40 ` Jason Molenda
2004-09-10 0:55 ` Michael Chastain
2004-09-10 0:58 ` Jason Molenda
2004-09-10 1:19 ` Daniel Jacobowitz
2004-09-10 23:13 ` [Committed] " Jason Molenda
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=414069F8.nailE691CTVHR@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jmolenda@apple.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