From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Subject: [obv] [mi] code cleanup: varobj_create variables move
Date: Fri, 06 Aug 2010 14:19:00 -0000 [thread overview]
Message-ID: <20100806141847.GA15006@host1.dyn.jankratochvil.net> (raw)
Checked-in.
http://sourceware.org/ml/gdb-cvs/2010-08/msg00024.html
--- src/gdb/ChangeLog 2010/08/05 16:19:18 1.12061
+++ src/gdb/ChangeLog 2010/08/06 14:17:55 1.12062
@@ -1,3 +1,9 @@
+2010-08-06 Jan Kratochvil <jan.kratochvil@redhat.com>
+
+ Code cleanup.
+ * varobj.c (varobj_create): Move variables fi, old_fi and block to
+ a more inner block.
+
2010-08-05 Pedro Alves <pedro@codesourcery.com>
* configure.tgt (alpha*-*-linux*, am33_2.0*-*-linux*, frv-*-*)
--- src/gdb/varobj.c 2010/05/17 18:48:52 1.158
+++ src/gdb/varobj.c 2010/08/06 14:17:56 1.159
@@ -528,9 +528,6 @@
char *expression, CORE_ADDR frame, enum varobj_type type)
{
struct varobj *var;
- struct frame_info *fi;
- struct frame_info *old_fi = NULL;
- struct block *block;
struct cleanup *old_chain;
/* Fill out a varobj structure for the (root) variable being constructed. */
@@ -539,6 +536,9 @@
if (expression != NULL)
{
+ struct frame_info *fi;
+ struct frame_info *old_fi = NULL;
+ struct block *block;
char *p;
enum varobj_languages lang;
struct value *value = NULL;
reply other threads:[~2010-08-06 14:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100806141847.GA15006@host1.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).