Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: Dirk Behme <dirk.behme@googlemail.com>, gdb@sourceware.org
Subject: Re: MI return error changed from 6.3 to 6.4?
Date: Sat, 08 Apr 2006 08:23:00 -0000	[thread overview]
Message-ID: <17462.57160.545635.736634@farnswood.snap.net.nz> (raw)
In-Reply-To: <20060407160222.GA24731@nevyn.them.org>

 > mi_cmd_interpreter_exec has conveniently returned MI_CMD_ERROR.
 > So, this should be easy to fix.  Thanks for the report.

However the manual says:

Manual>    To help users familiar with GDB's existing CLI interface, GDB/MI
Manual> accepts existing CLI commands.  As specified by the syntax, such
Manual> commands can be directly entered into the GDB/MI interface and GDB will
Manual> respond.

Manual>    This mechanism is provided as an aid to developers of GDB/MI clients
Manual> and not as a reliable interface into the CLI.  Since the command is
Manual> being interpreteted in an environment that assumes GDB/MI behaviour,
Manual> the exact output of such commands is likely to end up being an
Manual> un-supported hybrid of GDB/MI and CLI output.

so maybe we shouldn't fix it.

On the other hand this was written before the command -interpreter-exec.  If
entering CLI commands directly (using -interpreter-exec implicitly) can be
made as reliable as using -interpreter-exec explicitly, maybe this would be a
convenient alternative, and the above paragraph could be removed from the
manual.


-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2006-04-07 21:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-07 16:02 Dirk Behme
2006-04-07 17:36 ` Daniel Jacobowitz
2006-04-08  8:23   ` Nick Roberts [this message]
2006-04-08  9:57     ` Eli Zaretskii
2006-04-08 10:07       ` Nick Roberts
2006-04-08 18:35         ` Eli Zaretskii
2006-04-08 18:45           ` Nick Roberts

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=17462.57160.545635.736634@farnswood.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=dirk.behme@googlemail.com \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    /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