From: Daniel Jacobowitz <drow@false.org>
To: "jingzhao.ou" <jingzhao.ou@gmail.com>, gdb@sources.redhat.com
Subject: Re: Separating "shell dir" output from GDB/MI output
Date: Sun, 09 Oct 2005 20:26:00 -0000 [thread overview]
Message-ID: <20051009202652.GA7916@nevyn.them.org> (raw)
In-Reply-To: <20051009201923.GB972@white>
On Sun, Oct 09, 2005 at 04:19:23PM -0400, Bob Rossi wrote:
> On Sun, Oct 09, 2005 at 04:02:48PM -0400, Daniel Jacobowitz wrote:
> > On Sun, Oct 09, 2005 at 01:33:20PM -0400, Bob Rossi wrote:
> > > It solves several problems. The user no longer has to create a pty to
> > > give to GDB to separate the inferior output and the console output.
> > > (CGDB will have to anyways, since it uses the terminal).
> >
> > This one we've already solved, albeit with a bit of extra work on the
> > part of the frontend (and we were all enthusiastic about the solution,
> > too...)
>
> Sorry, I honestly can't remember what your talking about. What was the
> solution for this that the front end had to do? Also, don't forget, on
> windows nativly, the front end *can't* open a PTY. Eli came up with this
> solution for that problem,
> http://sources.redhat.com/ml/gdb-patches/2005-08/msg00047.html
All I mean is -inferior-set-tty.
> > > Some of the
> > > target's apparently write to STDOUT/STDERR, and that get's confused with
> > > the MI output.
> >
> > I don't know what you're referring to here.
>
> Oops, sorry. This is in the manual, and apparently is not true,
> target-stream-output is the output produced by the target program.
> All the target output is prefixed by `@'.
> We've had complaints by users that target output is not prefixed with
> '@'. So, I believe the output from the target can be intermingled with
> the MI output.
As far as I know this was never implemented except maybe for some remote
target.
> > > Finally, if we have several
> > > interpreters going at the same time, we could have them all output to
> > > there own descriptor.
> >
> > This is an interesting idea, but I don't think it's an obviously right
> > choice. The CLI frontend wants its own terminal, really. The MI
> > interpreter only needs a pipe. I have use for multiple MI interpreters
> > running at the same time, which will all need their own pipes, but
> > that's not a big deal with the infrastructure we already have.
>
> This is interesting. How would you start up GDB in such a scenario? Say
> you wanted 2 MI interpreters running. What would you do?
One of them is for the frontend. The other is for a Guile or Python
script being run, either by the user, or in a virtual "thread" in the
background watching for some interesting event. Only one of them would
have "focus" at a time, i.e. accept input; the others would receive
some set of event notifications.
That's my theory anyway. I started implementing this, and ran out of
steam. I haven't been back to it in a while.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-10-09 20:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-09 5:19 jingzhao.ou
2005-10-09 12:33 ` Bob Rossi
2005-10-09 17:04 ` jingzhao.ou
2005-10-09 17:12 ` Daniel Jacobowitz
2005-10-09 17:33 ` Bob Rossi
2005-10-09 20:02 ` Daniel Jacobowitz
2005-10-09 20:19 ` Bob Rossi
2005-10-09 20:26 ` Daniel Jacobowitz [this message]
[not found] ` <b5706cf10510091145v5bfa03ben44f62981f174c4a2@mail.gmail.com>
2005-10-09 18:47 ` jingzhao.ou
2005-10-09 20:04 ` Daniel Jacobowitz
2005-10-10 8:41 ` Re[2]: " Konstantin Karganov
2005-10-15 12:29 ` Eli Zaretskii
2005-10-15 12:27 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051009202652.GA7916@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=jingzhao.ou@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).