Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [mi] Some error path fixes
Date: Thu, 04 Jan 2007 21:59:00 -0000	[thread overview]
Message-ID: <20070104215914.GK24634@nevyn.them.org> (raw)
In-Reply-To: <20061207220013.GA9470@nevyn.them.org>

On Thu, Dec 07, 2006 at 05:00:13PM -0500, Daniel Jacobowitz wrote:
> 2006-12-07  Daniel Jacobowitz  <dan@codesourcery.com>
> 
> 	* Makefile.in (eval.o): Update dependencies.
> 	* eval.c: Include "ui-out.h" and "exceptions.h".
> 	(evaluate_subexp_standard): Use TRY_CATCH around value_of_variable.
> 	Use value_zero if an error occurs when avoiding side effects.
> 	* varobj.c (c_value_of_root): Initialize new_val.
> 
> 2006-12-07  Daniel Jacobowitz  <dan@codesourcery.com>
> 
> 	* gdb.mi/mi-var-cmd.exp: Add tests for unreadable varobjs.

I retested this and checked it in.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-01-04 21:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-07 22:00 Daniel Jacobowitz
2007-01-04 21:59 ` Daniel Jacobowitz [this message]
2007-03-09  0:55 ` Ulrich Weigand
2007-03-09  1:02   ` Daniel Jacobowitz
2007-03-09  1:16     ` Ulrich Weigand

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=20070104215914.GK24634@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@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