This is the mail archive of the
mailing list for the Cygwin project.
Re: No I/O redirection under GDB
- From: Eliot Moss <moss at cs dot umass dot edu>
- To: cygwin at cygwin dot com
- Date: Fri, 04 Apr 2014 22:51:24 -0400
- Subject: Re: No I/O redirection under GDB
- Authentication-results: sourceware.org; auth=none
- References: <20140405022905 dot GA8268 at dimstar dot local dot net>
- Reply-to: moss at cs dot umass dot edu
On 4/4/2014 10:29 PM, Duncan Roe wrote:
I just found that gdb's "run" command doesn't action redirection (e.g. run
</dev/pty2 >/dev/pty2 2>&1, where the shell on /dev/pty2 is doing a long sleep).
Instead, the invoked program gets the redirections as command line arguments.
Looking through the archives, I found
https://sourceware.org/ml/cygwin/1999-04/msg00355.html documenting this
behaviour. Chris Faylor commented at the time that fixing it was more trouble
than it appeared.
That was 15 years ago - has anything changed since? Anyone up for this or should
I have a go? I *could* simply make my target do the redirection itself, but that
doesn't help anyone else. OTOH if changing gdb really *is* that hard, maybe I
should just change my program anyway.
Any advice welcomed,
I think this is the intended design (see:
). If you want *gdb's* input and output redirected, I would think you want to invoke
gdb with I/O redirection on the command line, as in:
gdb foo < infile > outfile
Regards -- Eliot Moss
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple