From: Nick Roberts <nick@nick.uklinux.net>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Jim Ingham <jingham@apple.com>, gdb-patches@sources.redhat.com
Subject: Re: PATCH (gdb/mi)
Date: Sat, 01 Nov 2003 16:40:00 -0000 [thread overview]
Message-ID: <16291.61005.91144.786073@nick.uklinux.net> (raw)
In-Reply-To: <3FA17C13.3040300@redhat.com>
> Nick, MI changes need:
>
> - assignment
Who initiates this? I have done it for Emacs. Is it the same process for GDB
i.e REQUEST: SEND FORM FOR PAST AND FUTURE CHANGES to fsf-records@gnu.org
> - testcase
This is harder for me to do than the patch itself, so perhaps you can give me
a few clues. Will two tests for each of mi2-var-child.exp and mi1-var-child.exp
using "-var-list-children struct_declarations 0" and "-var-list-children
struct_declarations 1" suffice ?
> - doco
below
> - patch
Already sent.
If Jim can give you equivalent changes in the near future then that might be
the most simple route. If not, I would like to progress my changes through
the system.
Nick http://www.nick.uklinux.net
*** gdb.texinfo.~1.183.~ 2003-10-24 22:30:49.000000000 +0100
--- gdb.texinfo 2003-11-01 17:14:02.000000000 +0000
***************
*** 18121,18134 ****
@subsubheading Synopsis
@smallexample
! -var-list-children @var{name}
@end smallexample
! Returns a list of the children of the specified variable object:
@smallexample
numchild=@var{n},children=[@{name=@var{name},
numchild=@var{n},type=@var{type}@},@r{(repeats N times)}]
@end smallexample
--- 18121,18145 ----
@subsubheading Synopsis
@smallexample
! -var-list-children @var{name} [PRINT-VALUES]
@end smallexample
! Returns a list of the children of the specified variable object. With
! just the variable object name as an argument or with an optional
! second argument of 0, prints only the names of the variables. With an
! optional second argument of 1, also prints their values.
!
! @subsubheading Example
@smallexample
+ (@value{GDBP})
+ -var-list-children n
numchild=@var{n},children=[@{name=@var{name},
numchild=@var{n},type=@var{type}@},@r{(repeats N times)}]
+ (@value{GDBP})
+ -var-list-children n 1
+ numchild=@var{n},children=[@{name=@var{name},
+ numchild=@var{n},value=@var{VALUE},type=@var{type}@},@r{(repeats N times)}]
@end smallexample
next prev parent reply other threads:[~2003-11-01 16:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1067099552.15608.ezmlm@sources.redhat.com>
2003-10-27 19:02 ` Jim Ingham
2003-10-27 19:52 ` Eli Zaretskii
2003-10-30 21:01 ` Andrew Cagney
2003-10-31 17:57 ` Jim Ingham
2003-11-01 16:40 ` Nick Roberts [this message]
2003-11-03 14:35 ` Andrew Cagney
2003-11-21 17:41 ` Eli Zaretskii
2003-10-28 0:22 Nick Roberts
2003-10-28 6:44 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2003-10-25 16:32 Nick Roberts
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=16291.61005.91144.786073@nick.uklinux.net \
--to=nick@nick.uklinux.net \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jingham@apple.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