This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: gdb/remote - I/O
- To: Andrew Cagney <ac131313 at cygnus dot com>
- Subject: Re: gdb/remote - I/O
- From: Fernando Nasser <fnasser at redhat dot com>
- Date: Fri, 06 Apr 2001 14:43:55 -0400
- CC: GDB Discussion <gdb at sources dot redhat dot com>
- Organization: Red Hat Canada
- References: <3ABBDDE4.7C22709D@cygnus.com> <3ACE0AD6.913C9A94@cygnus.com>
Andrew Cagney wrote:
>
> Just an additional datapoint on this.
>
> The qRcmd packet (my fault) and the tracepoint packets (I've been
> reading C code) both use the existing ``O'' packet to send additional
> output back from the target during a query.
>
> The obvious question is where exactly that ``O'' packet is ment to be
> going - gdb_stdtarg, gdb_stdlog or gdb_stdout. If it is gdb_stdout and
> there is a pager things can get really complicated.
>
We do have two different kinds of output coming from the target: output
produced by the os/monitor/stub or whatever we are talking to and the
output from the application (little bit of semi-hosting).
Fortunately for us, they happen at different times. When the program is
running (after run or step) the output can be assumed to be from the
program and should go to gdb_stdtarg. When the program is not running
the output can only be from the controlling software, and we can send it
to gdb_stdout.
--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9