public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
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 [thread overview] Message-ID: <bug-16404-4717@http.sourceware.org/bugzilla/> (raw) 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.
next reply other threads:[~2014-01-07 17:52 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-07 17:52 jeff at approximatrix dot com [this message] 2015-07-03 14:47 ` [Bug mi/16404] " rw at firstpr dot com.au 2023-08-31 17:28 ` [Bug varobj/16404] " tromey at sourceware dot org
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=bug-16404-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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).