From: Christopher Faylor <cgf@redhat.com>
To: gdb@sources.redhat.com
Subject: Re: input redirection
Date: Wed, 23 Oct 2002 10:38:00 -0000 [thread overview]
Message-ID: <20021023173944.GD997@redhat.com> (raw)
In-Reply-To: <4EAA30E8E17684458E24408ADC13A4B501084EE5@esebe006.ntc.nokia.com>
On Wed, Oct 23, 2002 at 12:23:21PM +0300, antoine.trux@nokia.com wrote:
>P.S.: Yes, I searched the archives of gdb@sources.redhat.com and
>cygwin@sources.redhat.com, but found nothing helpful.
Hmm. You should have found some indication that input redirection isn't
currently functional in gdb for Windows whether it's the insight version
or the command line version.
There was some work added (from me) a while ago but it wasn't
functional. Pierre Mueller had some patches which helped but I didn't
like them so they didn't go in. I have an idea about how to do things
correctly but, for now, input redirection doesn't work.
cgf
next prev parent reply other threads:[~2002-10-23 17:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 2:23 antoine.trux
2002-10-23 10:38 ` Christopher Faylor [this message]
2002-10-23 10:59 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2002-10-12 4:07 Varun Kacholia
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=20021023173944.GD997@redhat.com \
--to=cgf@redhat.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