Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: nickrob@snap.net.nz (Nick Roberts)
To: Matt Rice <ratmice@gmail.com>
Cc: tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [patch/rfc] mi interpreter-complete enh req 8058.
Date: Sun, 04 Oct 2009 00:12:00 -0000	[thread overview]
Message-ID: <19143.59472.547182.54020@totara.tehura.co.nz> (raw)
In-Reply-To: <8ba6bed40910031159v6508a55ap4fd02b253c599794@mail.gmail.com>

 > Thanks, I had missed this CLI command somehow, it will work for now,
 > ideally i would like it not to be going directly to stdout like that
 > output infers, I guess i could change the output filehandle, when
 > executing this command until it finishes,  

I'm not sure what you mean.  Everything goes to stdout but you can
eliminate the LOG-STREAM-OUTPUT (prefixed by `&') by using
-interpreter-exec:

(gdb) 
-interpreter-exec console "complete b ma"
~"b main\n"
~"b malloc\n"
~"b malloc@plt\n"
^done
(gdb) 


 >                                           so that the output history
 > isn't filled with this temporal information which always bothers me...

You can use the server prefix to suppress commands being entered into
the command history.

 > additionally its worth noting the patch screws this output up.

Does that not show up in the testsuite?

What front end are you working on?


-- 
Nick                                           http://users.snap.net.nz/~nickrob


  reply	other threads:[~2009-10-04  0:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02 17:37 Matt Rice
2009-10-02 20:55 ` Tom Tromey
2009-10-02 23:10   ` Nick Roberts
2009-10-03 19:00     ` Matt Rice
2009-10-04  0:12       ` Nick Roberts [this message]
2009-10-05  8:00         ` Matt Rice

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=19143.59472.547182.54020@totara.tehura.co.nz \
    --to=nickrob@snap.net.nz \
    --cc=gdb-patches@sourceware.org \
    --cc=ratmice@gmail.com \
    --cc=tromey@redhat.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