From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com
Cc: gdb@sources.redhat.com
Subject: Re: how to call gdb_test "" ... ?
Date: Mon, 18 Feb 2002 15:33:00 -0000 [thread overview]
Message-ID: <200202182333.g1INXCS28517@duracef.shout.net> (raw)
Daniel Jacobowitz writes:
> Does gdb_test work with "\n"? I think it will. In fact, it appears to
> in casual testing.
Alas, gdb_test "\n" sends two carriage returns.
Michael C
next reply other threads:[~2002-02-18 23:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-18 15:33 Michael Elizabeth Chastain [this message]
2002-02-18 16:19 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2002-02-18 16:28 Michael Elizabeth Chastain
2002-02-18 15:46 Michael Elizabeth Chastain
2002-02-18 14:37 Michael Elizabeth Chastain
2002-02-18 15:16 ` Daniel Jacobowitz
2002-02-18 15:32 ` Keith Seitz
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=200202182333.g1INXCS28517@duracef.shout.net \
--to=mec@shout.net \
--cc=drow@mvista.com \
--cc=gdb@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