From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: Wu Zhou <woodzltc@cn.ibm.com>, gdb-patches@sources.redhat.com
Subject: Re: PATCH: Start Fortran support for variable objects.
Date: Mon, 04 Jul 2005 01:42:00 -0000 [thread overview]
Message-ID: <17096.37817.638887.840041@farnswood.snap.net.nz> (raw)
In-Reply-To: <20050703234725.GA28151@nevyn.them.org>
> > > First of all, never reference ->main_type - see above for the right way
> > > to get the low bound. An even better way (it seems) is to call
> > > get_discrete_bounds. Take a look at value_subscript for an example.
> >
> > Better than TYPE_LOW_BOUND?
>
> I suppose. I don't know which one is preferred; some day, someone
> should go through and clean them all up to be consistent. I'm fine
> with either choice.
To keep things simple I've used TYPE_LOW_BOUND. I've tested with the examples
I've posted before and it works. Presumably there should also be a test case,
so I'll create one for mi-var-child.exp and mi2-var-child.exp (you still
haven't approved my patch for mi2-cmd-stack.exp (28 Jun 2005 01:53:52 +1200).
In particular, this patch does eliminate the need for the fortran-specific
code.
Nick
2005-06-30 Nick Roberts <nickrob@snap.net.nz>
* varobj.c (varobj_list_children): Allow non-zero offsets for
languages like Fortran.
Index: varobj.c
===================================================================
RCS file: /cvs/src/src/gdb/varobj.c,v
retrieving revision 1.54
diff -u -p -r1.54 varobj.c
--- varobj.c 26 Apr 2005 05:03:37 -0000 1.54
+++ varobj.c 4 Jul 2005 01:36:54 -0000
@@ -696,7 +696,7 @@ varobj_list_children (struct varobj *var
{
struct varobj *child;
char *name;
- int i;
+ int i, j, retcode;
/* sanity check: have we been passed a pointer? */
if (childlist == NULL)
@@ -715,11 +715,13 @@ varobj_list_children (struct varobj *var
/* Mark as the end in case we bail out */
*((*childlist) + i) = NULL;
+ j = i + TYPE_LOW_BOUND (TYPE_INDEX_TYPE (var->type));
+
/* check if child exists, if not create */
- name = name_of_child (var, i);
+ name = name_of_child (var, j);
child = child_exists (var, name);
if (child == NULL)
- child = create_child (var, i, name);
+ child = create_child (var, j, name);
*((*childlist) + i) = child;
}
next prev parent reply other threads:[~2005-07-04 1:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 21:28 Nick Roberts
2005-06-30 2:53 ` Daniel Jacobowitz
2005-06-30 9:28 ` Nick Roberts
2005-06-30 13:15 ` Daniel Jacobowitz
2005-06-30 22:21 ` Nick Roberts
2005-06-30 22:23 ` Daniel Jacobowitz
2005-06-30 13:18 ` Daniel Jacobowitz
2005-06-30 22:21 ` Nick Roberts
2005-07-01 3:35 ` Wu Zhou
2005-07-01 5:04 ` Nick Roberts
2005-07-01 12:00 ` Wu Zhou
2005-07-03 16:17 ` Daniel Jacobowitz
2005-07-03 23:40 ` Nick Roberts
2005-07-03 23:47 ` Daniel Jacobowitz
2005-07-04 1:42 ` Nick Roberts [this message]
2005-07-04 3:49 ` Daniel Jacobowitz
2005-07-04 7:35 ` Nick Roberts
2005-07-05 3:43 ` Nick Roberts
2006-03-13 14:08 ` Nick Roberts
2006-03-24 22:58 ` Daniel Jacobowitz
2006-03-27 1:25 ` Nick Roberts
2006-03-27 4:04 ` Daniel Jacobowitz
2006-03-27 4:24 ` Nick Roberts
2006-03-27 11:32 ` Daniel Jacobowitz
2005-07-06 8:31 ` Wu Zhou
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=17096.37817.638887.840041@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=woodzltc@cn.ibm.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