Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: "J. Johnston" <jjohnstn@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Patch for gdb/mi problem 672
Date: Mon, 30 Sep 2002 13:11:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0209300936040.1514-100000@valrhona.uglyboxes.com> (raw)
In-Reply-To: <3D94DB49.BF3C3520@redhat.com>

Hi,

Although I know that varobj shouldn't longjmp in case of errors, I don't 
think that this is going to be a safe assumption. I would recommend that 
you refrain from using ui_out_*_begin and ui_out_*_end, and instead use 
make_cleanup_ui_out_*_begin_end and do_cleanups, which will make sure that 
the UIOUT builder is properly reset in case of errors. (See, for example, 
the cleanup that I did in mi_cmd_data_list_registers.)

On Fri, 27 Sep 2002, J. Johnston wrote:

> @@ -419,10 +419,10 @@
>    if ((*name == '*') && (*(name + 1) == '\0'))
>      {
>        nv = varobj_list (&rootlist);
> -      ui_out_tuple_begin (uiout, "changelist");
> +      ui_out_list_begin (uiout, "changelist");
>        if (nv <= 0)
>  	{
> -	  ui_out_tuple_end (uiout);
> +	  ui_out_list_end (uiout);
>  	  return MI_CMD_DONE;
>  	}
>        cr = rootlist;

[Andrew has already addressed the MI0 thing...]

Other than that, I would recommend that it be approved (for whatever 
that's worth).

Keith



  reply	other threads:[~2002-09-30 20:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-27 15:27 J. Johnston
2002-09-30 13:11 ` Keith Seitz [this message]
2002-09-30 14:13   ` Elena Zannoni
2002-09-30 18:07     ` Andrew Cagney
2002-10-02 10:49   ` J. Johnston
2002-10-02 15:54     ` Andrew Cagney
2002-10-02 15:55     ` Andrew Cagney

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=Pine.LNX.4.44.0209300936040.1514-100000@valrhona.uglyboxes.com \
    --to=keiths@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jjohnstn@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