public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "elethiomel at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug mi/10586] Anonymous unions/structs not handled correctly under MI
Date: Sat, 10 Oct 2009 02:23:00 -0000	[thread overview]
Message-ID: <20091010022331.5250.qmail@sourceware.org> (raw)
In-Reply-To: <20090901200751.10586.elethiomel@gmail.com>


------- Additional Comments From elethiomel at gmail dot com  2009-10-10 02:23 -------
Thanks for looking at this. I have applied the patch to the latest cvs snapshot
of GDB (7.0.50.20091009) and still get "Duplicate variable object name" using
the posted testcase. Here's the debugger session.

(gdb) 
343-stack-list-arguments 0 0 0
343^done,stack-args=[frame={level="0",args=[]}]
(gdb) 
344-stack-list-locals 0
344^done,locals=[name="bar"]
(gdb) 
345 whatis bar
&"whatis bar\n"
~"type = test\n"
345^done
(gdb) 
346 ptype test
&"ptype test\n"
~"type = struct test {\n"
~"    test::<anonymous struct>;\n"
~"    test::<anonymous struct>;\n"
~"}\n"
346^done
(gdb) 
347-var-create - * bar
347^done,name="var1",numchild="1",value="{...}",type="test",thread-id="1",has_more="0"
(gdb) 
348-var-evaluate-expression var1
348^done,value="{...}"
(gdb) 
349-var-show-attributes var1
349^done,attr="noneditable"
(gdb) 
350-data-evaluate-expression bar
350^done,value="{{a = 1209049076, b = 3.9881805e-34}, {c = 134514617, d =
148095.812}}"
(gdb) 
351-var-list-children var1
351^done,numchild="1",children=[child={name="var1.public",exp="public",numchild="2",thread-id="1"}],has_more="0"
(gdb) 
352-var-info-expression var1
352^done,lang="C++",exp="bar"
(gdb) 
353-var-list-children var1.public
353^error,msg="Duplicate variable object name"
(gdb) 
354-var-list-children var1
354^done,numchild="1",children=[child={name="var1.public",exp="public",numchild="2",thread-id="1"}],has_more="0"
(gdb) 
355-var-list-children var1.public
355^error,msg="Duplicate variable object name"
(gdb) 
356-data-evaluate-expression bar
356^done,value="{{a = 1209049076, b = 3.9881805e-34}, {c = 134514617, d =
148095.812}}"
(gdb) 

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=10586

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2009-10-10  2:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-01 20:07 [Bug mi/10586] New: " elethiomel at gmail dot com
2009-09-01 20:11 ` [Bug mi/10586] " tromey at redhat dot com
2009-09-01 21:14 ` elethiomel at gmail dot com
2009-10-08 16:57 ` elethiomel at gmail dot com
2009-10-10  0:42 ` nickrob at snap dot net dot nz
2009-10-10  2:23 ` elethiomel at gmail dot com [this message]
2009-10-10  3:10 ` nickrob at snap dot net dot nz
2009-10-10  3:33 ` nickrob at snap dot net dot nz
2009-10-10 13:27 ` elethiomel at gmail dot com
2009-10-10 22:35 ` nickrob at snap dot net dot nz
2009-10-10 22:56 ` elethiomel at gmail dot com
2009-10-11  0:36 ` nickrob at snap dot net dot nz
     [not found] <bug-10586-4717@http.sourceware.org/bugzilla/>
2011-11-11 21:32 ` keiths at redhat dot com
2012-01-12 22:51 ` cvs-commit at gcc dot gnu.org
2012-01-12 22:52 ` cvs-commit at gcc dot gnu.org
2012-01-12 22:55 ` keiths at redhat dot com

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=20091010022331.5250.qmail@sourceware.org \
    --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: 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).