Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: RFC: selected frame in read_var_value
Date: Fri, 01 Aug 2003 19:29:00 -0000	[thread overview]
Message-ID: <20030801192951.GA2109@nevyn.them.org> (raw)

Thoughts on this?  I observed one case where the selected frame hadn't been
initialized yet: when checking watchpoint values.  Oops!  The condition
matches the case in which get_current_frame () can be reasonably expected to
succeed.  There are a couple other places that need this same check, mostly
functions which will work on globals as well as locals.

An alternative would be to create a lifeless_frame and have
get_current_frame return that when there is no running target; have it call
error if a register is read, its base is requested, et cetera.  I suspect
that would require some serious surgery.  We'd also need to pass
lifeless_frame everywhere we could be passing a NULL frame now.  For
instance, several callers of read_var_value will give it no frame.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

2003-08-01  Daniel Jacobowitz  <drow@mvista.com>

	* findvar.c (read_var_value): If the target is running, call
	get_selected_frame instead of checking deprecated_selected_frame.

--- gdb-5.3.20030801/gdb/findvar.c.orig	2003-08-01 14:46:12.000000000 -0400
+++ gdb-5.3.20030801/gdb/findvar.c	2003-08-01 14:50:27.000000000 -0400
@@ -388,7 +388,7 @@ symbol_read_needs_frame (struct symbol *
    and a stack frame id, read the value of the variable
    and return a (pointer to a) struct value containing the value. 
    If the variable cannot be found, return a zero pointer.
-   If FRAME is NULL, use the deprecated_selected_frame.  */
+   If FRAME is NULL, use the selected frame.  */
 
 struct value *
 read_var_value (register struct symbol *var, struct frame_info *frame)
@@ -404,8 +404,9 @@ read_var_value (register struct symbol *
 
   len = TYPE_LENGTH (type);
 
-  if (frame == NULL)
-    frame = deprecated_selected_frame;
+  if (frame == NULL && target_has_registers && target_has_stack
+      && target_has_memory)
+    frame = get_selected_frame ();
 
   switch (SYMBOL_CLASS (var))
     {


             reply	other threads:[~2003-08-01 19:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-01 19:29 Daniel Jacobowitz [this message]
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
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=20030801192951.GA2109@nevyn.them.org \
    --to=drow@mvista.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