From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb-patches@sources.redhat.com
Subject: Re: gdb.texinfo patch for -var-list-children (2)
Date: Sat, 20 Jun 2009 08:45:00 -0000 [thread overview]
Message-ID: <h1i7b2$ekr$2@ger.gmane.org> (raw)
In-Reply-To: <ed4903890906192111v3c6da578ydaddef059f9fe1e1@mail.gmail.com>
Chris Genly wrote:
> Description
>
> The gdb documentation for the MI command -var-list-children does not
> define the exp
> result for a child. Exp and other child results documented.
>
> Sorry I didn't document this with the last patch. But my
> understanding of MI commands is still increasing.
>
> Change log
>
> 2009-06-19 Chris Genly <chris@genly.us>
> * doc/gdb.texinfo (GDB/MI Variable Objects): Document child
> definition in -var-list-children. Added exp result for child.
>
> Patch
>
> Index: gdb.texinfo
> ===================================================================
> RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
> retrieving revision 1.600
> diff -c -p -r1.600 gdb.texinfo
> *** gdb.texinfo 15 Jun 2009 12:11:36 -0000 1.600
> --- gdb.texinfo 20 Jun 2009 04:07:54 -0000
> *************** Returns the format used to display the v
I suggest you use unified diffs for patches (cvs diff -u). The default "context"
format is some historically-inflicted thing that is hard to read.
- Volodya
next prev parent reply other threads:[~2009-06-20 8:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-20 4:11 Chris Genly
2009-06-20 8:45 ` Vladimir Prus [this message]
2009-06-20 10:01 ` Eli Zaretskii
2009-06-22 3:18 ` Joel Brobecker
2009-06-22 4:42 ` Eli Zaretskii
2009-06-22 15:02 ` Daniel Jacobowitz
2009-06-23 1:00 ` Eli Zaretskii
2009-06-23 3:19 ` Daniel Jacobowitz
2009-06-20 15:18 ` Eli Zaretskii
2009-06-20 20:31 ` Chris Genly
2009-06-20 21:33 ` Chris Genly
2009-07-04 12:13 ` Eli Zaretskii
2009-06-20 23:12 ` Eli Zaretskii
2009-06-20 23:17 ` Samuel Bronson
2009-06-21 19:28 ` Chris Genly
2009-06-21 23:12 ` Eli Zaretskii
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='h1i7b2$ekr$2@ger.gmane.org' \
--to=vladimir@codesourcery.com \
--cc=gdb-patches@sources.redhat.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