Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFC: selected frame in read_var_value
Date: Mon, 08 Sep 2003 13:37:00 -0000	[thread overview]
Message-ID: <20030908133727.GA17816@nevyn.them.org> (raw)
In-Reply-To: <3F5C852D.2010207@redhat.com>

On Mon, Sep 08, 2003 at 09:33:33AM -0400, Andrew Cagney wrote:
> 
> >Is this about what you wanted, and are my comments on the mark?
> 
> Yes, just one pedantic tweak.
> 
> >If so, how do you feel about a mass replacement of the one deprecated
> >construct (deprecated_selected_frame) with the new deprecated construct
> >(deprecated_safe_get_selected_frame) in the places in GDB which use
> >this "if frame arg is NULL, get selected frame" idiom?
> 
> For 6.0, scares the peverbial out of me -> got a convincing argument? 
> :-)  For the mainline, not phased.

I don't know if it's convincing, but I've had one bug reported that
would be fixed by it (assertion failure in -data-list-changed-registers).
I've got another one to look at now that might be similar.  We could
just do 'em as they're discovered.

> 
> Andrew
> 
> 
> >+/* This is a variant of get_selected_frame which can be called when the
> >+   inferior is not running; in that case it will return NULL instead of
> >+   calling error ().  */
> 
> Almost.  Those are also true for a core file.

Ooh, that's right of course.  I'll revise and commit.

> 
> >+struct frame_info *
> >+deprecated_safe_get_selected_frame (void)
> >+{
> >+  if (!target_has_registers || !target_has_stack || !target_has_memory)
> >+    return NULL;
> >+  return get_selected_frame ();
> >+}
> 
> 
> 
> 
> 

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-09-08 13:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-01 19:29 Daniel Jacobowitz
2003-08-07 17:45 ` Andrew Cagney
2003-08-28 19:55   ` Daniel Jacobowitz
2003-09-05 17:14     ` Andrew Cagney
2003-09-05 17:18       ` Daniel Jacobowitz
2003-09-05 17:39         ` Andrew Cagney
2003-09-07  3:53       ` Daniel Jacobowitz
2003-09-08 13:33         ` Andrew Cagney
2003-09-08 13:37           ` Daniel Jacobowitz [this message]
2003-09-08 18:59           ` Daniel Jacobowitz
2004-02-08  4:17           ` Daniel Jacobowitz
2004-02-08 17:33             ` 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=20030908133727.GA17816@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@redhat.com \
    --cc=gdb-patches@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