From: Andrew Cagney <cagney@gnu.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: MI output change
Date: Tue, 08 Feb 2005 16:30:00 -0000 [thread overview]
Message-ID: <4208E71A.5070307@gnu.org> (raw)
In-Reply-To: <41E8316F.7050806@gnu.org>
Andrew Cagney wrote:
Two ya's, no Na's. All but 'done' :-/
> Hello,
>
> The MI output is currently littered with:
>
> (gdb)
> PASS: gdb.mi/mi-var-cmd.exp: create lsimple->integer
> -var-create int * int
> &"Attempt to use a type name as an expression.\n"
> &"mi_cmd_var_create: unable to create variable object\n"
> ^error,msg="mi_cmd_var_create: unable to create variable object"
> (gdb)
>
> (note how the error appears as both the result and as standard out)
>
> My recent exception handling rewrite means that this can finally be
> fixed. However that means that the MI output has technically changed -
> no one should be relying on the message appearing on stdout but hey ...
>
> Is this going to be an issue?
>
> Andrew
>
next prev parent reply other threads:[~2005-02-08 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 20:56 Andrew Cagney
2005-01-15 1:37 ` Bob Rossi
2005-02-08 16:30 ` Andrew Cagney [this message]
2005-02-09 4:51 ` Bob Rossi
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=4208E71A.5070307@gnu.org \
--to=cagney@gnu.org \
--cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).