MI interface
Keith Seitz
keiths@redhat.com
Wed Sep 18 09:03:00 GMT 2002
On Wed, 18 Sep 2002, Arjan van Dijk wrote:
> >Why does gdb redirect the stdout to itself? I mean due to this all programs
>
> and I would like to know too!
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=623&return_url=http%3A%2F%2Fsources.redhat.com%2Fcgi-bin%2Fgnatsweb.pl%3Fdatabase%3Dgdb%26category%3Dall%26severity%3Dall%26priority%3Dall%26responsible%3Dall%26submitter_id%3Dall%26state%3Dall%26ignoreclosed%3DIgnore%2520Closed%26class%3Dall%26synopsis%3D%26multitext%3D%26columns%3Dcategory%26columns%3Dstate%26columns%3Dclass%26columns%3Dresponsible%26columns%3Dsynopsis%26displaydate%3DDisplay%2520Current%2520Date%26cmd%3Dsubmit%2520query%26sortby%3DResponsible%26.cgifields%3Dcolumns%26.cgifields%3Doriginatedbyme%26.cgifields%3Ddisplaydate%26.cgifields%3Dignoreclosed
Basically the problem is that in order for this to work on a native
target, that target must be async. Right now there are no async native
targets. I hope to correct that when I've got some more cycles.
This is still a very, very tricky situation, though. While many programs
will work with just this target output, I would suspect that many
applications simply won't work (well) this way. Imagine trying to debug
emacs or vi -- the developer is almost certainly going to want to use a
separate tty for the inferior. Unless the UI developer is willing (or
crazy enough) to implement a terminal emulator in the IDE/GUI, these more
sophisticated programs just aren't going to work properly.
Keith
More information about the Gdb
mailing list