This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

NOT WORKED AROUND Re: No I/O redirection under GDB

Sorry for the noise everyone.

I started to compose the last mail thinking "set inferior-tty" would solve my
problem. Then on further testing, I found it didn't.

I'm still up for fixing gdb to do the job properly - or can someone on this list
tell me why I'd be wasting my time?

Cheers ... Duncan.

On Sat, Apr 05, 2014 at 03:15:14PM +1100, Duncan Roe wrote:
> On Fri, Apr 04, 2014 at 10:51:24PM -0400, Eliot Moss wrote:
> > 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
> > > 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
> >
> Thanks for replying.
> Sorry but your suggested command line doesn't help: I need gdb command i/o in
> one screen and program i/o in another.
> The set inferior-tty command documented in the link you posted *very nearly*
> gave me what I was after. Having updated my startup script to use it, I now find
> that I can't use Control-C to interrupt the session: it's ignored in the gdb
> window and causes catastrophic gdb failure in the application window (as well as
> waking the shell from sleep). It's better than nothing I guess.
> So, I'm back to needing i/o redirection in the run command (as also documented
> in your link). It works in Linux.
> Cheers ... Duncan.

Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]