From: Keven Boell <keven.boell@linux.intel.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] testsuite: introduce index in varobj child eval.
Date: Wed, 27 Nov 2013 13:49:00 -0000 [thread overview]
Message-ID: <5295E492.7050501@linux.intel.com> (raw)
In-Reply-To: <87fvqj5h3e.fsf@fleche.redhat.com>
Thanks for the feedback. I've attached the updated patch, which
addresses your comments.
Keven
From 7c6728c1f92f92b54310ca1d74e113e6300e2ba4 Mon Sep 17 00:00:00 2001
From: Keven Boell <keven.boell@intel.com>
Date: Thu, 21 Nov 2013 10:54:47 +0100
Subject: [PATCH] testsuite: introduce index in varobj child eval.
In some languages, e.g. fortran, arrays start with index 1
instead 0. This patch changes the MI library to support testing
varobj children of fortran arrays.
2013-11-21 Keven Boell <keven.boell@intel.com>
testsuite/
* lib/mi-support.exp (mi_list_varobj_children_range): Add
call to mi_list_array_varobj_children_with_index.
(mi_list_array_varobj_children_with_index): New function.
Add parameter to specify array start.
Signed-off-by: Keven Boell <keven.boell@intel.com>
---
gdb/testsuite/lib/mi-support.exp | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/gdb/testsuite/lib/mi-support.exp
b/gdb/testsuite/lib/mi-support.exp
index 0c3cdbe..cb7bf90 100644
--- a/gdb/testsuite/lib/mi-support.exp
+++ b/gdb/testsuite/lib/mi-support.exp
@@ -1487,9 +1487,18 @@ proc mi_list_varobj_children_range {varname from
to numchildren children testnam
# Verifies that variable object VARNAME has NUMBER children,
# where each one is named $VARNAME.<index-of-child> and has type TYPE.
proc mi_list_array_varobj_children { varname number type testname } {
+ mi_list_array_varobj_children_with_index $varname $number 0 $type
$testname
+}
+
+# Same as mi_list_array_varobj_children, but allowing to pass a start index
+# for an array.
+proc mi_list_array_varobj_children_with_index { varname number
start_index \
+ type testname } {
set t {}
+ set index $start_index
for {set i 0} {$i < $number} {incr i} {
- lappend t [list $varname.$i $i 0 $type]
+ lappend t [list $varname.$index $index 0 $type]
+ incr index
}
mi_list_varobj_children $varname $t $testname
}
--
1.7.9.5
On 26.11.2013 16:16, Tom Tromey wrote:
>>>>>> "Keven" == Keven Boell <keven.boell@intel.com> writes:
>
> Keven> # Verifies that variable object VARNAME has NUMBER children,
> Keven> # where each one is named $VARNAME.<index-of-child> and has type TYPE.
> Keven> proc mi_list_array_varobj_children { varname number type testname } {
> Keven> + mi_list_array_varobj_children_with_index $varname $number 0 $type $testname
> Keven> +}
> Keven> +proc mi_list_array_varobj_children_with_index { varname number start_index type testname } {
>
> The new proc should be separated from the previous one by a blank line.
> It should have an introductory comment as well.
>
> Also the first line of the new proc is too long. I think it should be
> split in the arglist somewhere.
>
> Tom
>
next prev parent reply other threads:[~2013-11-27 12:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 13:35 Keven Boell
2013-11-26 16:16 ` Tom Tromey
2013-11-27 13:49 ` Keven Boell [this message]
2013-11-27 15:58 ` Tom Tromey
2013-11-28 12:25 ` Keven Boell
2013-12-03 20:24 ` Tom Tromey
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=5295E492.7050501@linux.intel.com \
--to=keven.boell@linux.intel.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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