From: Vladimir Prus <ghost@cs.msu.su>
To: Nick Roberts <nickrob@snap.net.nz>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Fix variable objects for references to pointers
Date: Thu, 21 Dec 2006 15:25:00 -0000 [thread overview]
Message-ID: <E1GxPnE-00056s-FX@zigzag.lvk.cs.msu.su> (raw)
In-Reply-To: <17793.7666.771432.41360@kahikatea.snap.net.nz>
Nick Roberts wrote:
> 2006-12-14  Nick Roberts  <nickrob@snap.net.nz>
>
> * gdb.mi/mi-var-cp.exp: New test for references to pointers.
>
> * gdb.mi/mi-var-cp.cc: Remove unnecessary string quotes.
This comment likely applies to .exp file, not .cc. Besides,
it would be better not to mix style changes with essential changes,
to simplify review.
Ah, and I've posted a patch to move most of .exp into .cc file,
so I guess we've mid-air collision.
> (reference_to_pointer): New procedure for above test.
Am I missing something, or this change is not included in
your mail? Ah, I think it's the CVS problem, whereas added
files are not included in diff.
> + set end_of_proc [gdb_get_line_number "return 99;"]
> + send_gdb "-exec-next 4\n"
> + gdb_expect {
> + Â Â -re
> "\\^running\r\n${mi_gdb_prompt}\\*stopped,reason=\"end-stepping-range\",thread-id=\"\[01\]\",frame=\{addr=\"$hex\",func=\"reference_to_pointer\",args=\\\[\\\],file=\".*${srcfile}\",fullname=\"${fullname_syntax}${srcfile}\",line=\"$end_of_proc\"\}\r\n$mi_gdb_prompt$"
> { + Â Â Â Â Â Â pass "4xnext to return 99" + Â Â }
> + Â Â timeout { fail "4xnext in reference_to_pointer (timeout)" }
> + }
FWIW, once my "Simplified MI tests" patch is checked in, this block
can be just removed.
> +
> + mi_create_varobj RPTR rptr_s "create varobj for rptr_s"
> +
> + mi_list_varobj_children RPTR {{RPTR.public public 2}} \
> + Â Â "list public child of RPTR"
> +
> + mi_list_varobj_children  RPTR.public \
> + Â Â {{RPTR.public.i i 0 int}
> + Â Â Â {RPTR.public.j j 0 int}} "list children of reference to pointer"
> +
> + mi_check_varobj_value RPTR.public.i 67 "check i member"
> + mi_check_varobj_value RPTR.public.j 89 "check j member"
Looks good. I've poked at this manually and it seems to work like
it should.
Now I guess you need to post a patch including the C++ file changes,
now that it's in CVS, and we need to find somebody who can actually
approve the patch.
Thanks,
Volodya
next prev parent reply other threads:[~2006-12-21 15:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 4:58 Nick Roberts
2006-12-14 6:03 ` Vladimir Prus
2006-12-14 9:53 ` Nick Roberts
2006-12-21 15:25 ` Vladimir Prus [this message]
2006-12-21 22:38 ` Nick Roberts
2007-01-03 22:55 ` Daniel Jacobowitz
2007-01-04 9:42 ` Nick Roberts
2007-01-04 11:56 ` Vladimir Prus
2007-01-04 14:09 ` Daniel Jacobowitz
2007-01-04 22:30 ` Nick Roberts
2007-01-04 22:33 ` Daniel Jacobowitz
2007-01-03 22:49 ` Daniel Jacobowitz
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=E1GxPnE-00056s-FX@zigzag.lvk.cs.msu.su \
--to=ghost@cs.msu.su \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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