public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: "jingzhao.ou" <jingzhao.ou@gmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: Separating "shell dir" output from GDB/MI output
Date: Sun, 09 Oct 2005 20:04:00 -0000	[thread overview]
Message-ID: <20051009200400.GB7166@nevyn.them.org> (raw)
In-Reply-To: <b5706cf10510091147x2bb8cfcexacc9b6fe1d74cfcd@mail.gmail.com>

On Sun, Oct 09, 2005 at 11:47:20AM -0700, jingzhao.ou wrote:
> interpreter-exec can give me what I am looking for. However, its
> output is mixed with the MI output and will confuse Bob's parser. :-(
> 
> interpreter-exec console "b main"
> &"interpreter-exec console \"b main\"\n"
> Breakpoint 1 at 0x4012e7: file gdbmi_driver.c, line 14.
> ^done
> (gdb)
> 
> It seems that support of multiple file descriptors is a potential
> solution for such problems.

IIRC this is exactly what console-quoted was for.

Ideally, IMO, we should have the CLI as a true frontend rather than
interwoven with gdb.  I don't know if that's practical.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

  reply	other threads:[~2005-10-09 20:04 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
     [not found]       ` <b5706cf10510091145v5bfa03ben44f62981f174c4a2@mail.gmail.com>
2005-10-09 18:47         ` jingzhao.ou
2005-10-09 20:04           ` Daniel Jacobowitz [this message]
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=20051009200400.GB7166@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).