From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-prs-return-14999-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Received: (qmail 1660 invoked by alias); 7 Jan 2014 17:52:49 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Received: (qmail 1634 invoked by uid 48); 7 Jan 2014 17:52:49 -0000
From: "jeff at approximatrix dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug mi/16404] New: -var-set-update-range ignored on update
Date: Tue, 07 Jan 2014 17:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: mi
X-Bugzilla-Version: 7.6
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jeff at approximatrix dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
 bug_severity priority component assigned_to reporter
Message-ID: <bug-16404-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-q1/txt/msg00007.txt.bz2

https://sourceware.org/bugzilla/show_bug.cgi?id=16404

            Bug ID: 16404
           Summary: -var-set-update-range ignored on update
           Product: gdb
           Version: 7.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mi
          Assignee: unassigned at sourceware dot org
          Reporter: jeff at approximatrix dot com

Unless I am mistaken, -var-set-update-range does not seem to have any affect on
children that are updated.  Consider the following program:

#include <stdio.h>

int main(int argc, char *argv[])
{
int i;
int arr[512];

    printf("Starting up\n");

    for(i=0;i<512;i++)
        arr[i] = 3;

    printf("Assigned %d\n", i);

    return 0;
}

When I run the program via gdb, I'm using the following sequence of commands
via mi2:

=====
(gdb)
start
... plenty of output ...
(gdb)
-var-create v1 * arr
^done,name="v1",numchild="512",value="[512]",type="int
[512]",thread-id="1",has_more="0"
(gdb)
-var-list-children v1 0 2
^done,numchild="2",children=[child={name="v1.0",exp="0",numchild="0",type="int",thread-id="1"},child={name="v1.1",exp="1",numchild="0",type="int",thread-id="1"}],has_more="1"
(gdb)
break main.c:13
... plenty of output ...
(gdb)
cont
... plenty of output, break reached after loop ...
(gdb)
-var-set-update-range v1 0 2
^done
(gdb)
-var-update v1
... every child of v1 is now listed (512 in fact) ...
====

Perhaps I'm missing a detail, but I expect only to see the first to entries of
`arr` to be output.  I realize the above mixes console and mi2 commmands, but
it shouldn't be an issue.

-- 
You are receiving this mail because:
You are on the CC list for the bug.