From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Tromey To: Paul Dubuc Cc: Orjan Friberg , Grant Edwards , gdb@sourceware.cygnus.com Subject: Re: Redirect GDB command output? Date: Fri, 05 Oct 2001 11:27:00 -0000 Message-id: <87vghuszgw.fsf@creche.redhat.com> References: <3BBB60BB.BB99CB3F@cas.org> <20011005092623.A1275@visi.com> <3BBDCDD9.6E281600@axis.com> <3BBDE11F.F55360ED@cas.org> X-SW-Source: 2001-10/msg00067.html >>>>> "Paul" == Paul Dubuc writes: Paul> No, I was looking for something more like the redirect Paul> capability for the output of individual commands from the gdb Paul> prompt. Some dbx functions our project uses rely on this Paul> capability in dbx and (unfortunately) I see no way of Paul> reproducing those functions with gdb user-defined commands. I don't think it would be very hard to write `>' (redirect) and `>>' (redirect-append) commands for gdb. Maybe you could even have a `|' command that would pipe output through another process (this might be harder due to portability constraints). The easiest way to do this would be to have prefix commands. For instance `> file command' would run command with output redirected to file. `> file' would redirect output for all subsequence command lines. Plain `>' would then stop redirecting the output. Likewise for `>>'. Something like `|' would probably need a slightly different syntax (for instance simply disallow a trailing gdb command). Using a prefix command feels a bit strange, but I implementation-wise is probaby much, much easier. Tom