From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sources.redhat.com
Cc: gdb@sources.redhat.com
Subject: Re: RFC: GDB as a loader 1/3: silent batch mode
Date: Sat, 29 Oct 2005 10:32:00 -0000 [thread overview]
Message-ID: <u64rgsjf3.fsf@gnu.org> (raw)
In-Reply-To: <20051028203836.GA3849@nevyn.them.org> (message from Daniel Jacobowitz on Fri, 28 Oct 2005 16:38:36 -0400)
> Date: Fri, 28 Oct 2005 16:38:36 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Andrew STUBBS <andrew.stubbs@st.com>, gdb@sources.redhat.com
>
> On Fri, Oct 28, 2005 at 07:23:18PM +0200, Eli Zaretskii wrote:
> > > Date: Fri, 28 Oct 2005 14:55:57 +0100
> > > From: Andrew STUBBS <andrew.stubbs@st.com>
> > > Cc: gdb@sources.redhat.com
> > >
> > > I was just using: make gdb.pdf
> > >
> > > The gdb.log file is attached. Maybe you can make more sense of it than I
> > > can.
> >
> > I think I fixed the problem that caused this, but I cannot verify
> > right now, since I don't have the necessary stuff installed where I
> > type this. Could you please resync with the CVS repository and try
> > "make gdb.pdf" again?
>
> Hi Eli,
>
> Could you please post the patch to gdb-patches? That's our standard
> practice for every change, no matter how trivial.
Sorry, forgot about that. Here it is. As you see, it was incorrect
usage of @pxref.
2005-10-28 Eli Zaretskii <eliz@gnu.org>
* gdb.texinfo (GDB/MI Variable Objects): Fix @pxref usage under
"The -var-update Command".
Index: gdb/doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.280
retrieving revision 1.281
diff -u -r1.280 -r1.281
--- gdb/doc/gdb.texinfo 3 Oct 2005 22:26:54 -0000 1.280
+++ gdb/doc/gdb.texinfo 28 Oct 2005 17:20:03 -0000 1.281
@@ -20636,9 +20636,9 @@
Update the value of the variable object @var{name} by evaluating its
expression after fetching all the new values from memory or registers.
A @samp{*} causes all existing variable objects to be updated. The
-option @var{print-values} determines whether names and values, or just
-names are printed in the manner described for
-@code{@pxref{-var-list-children}}.
+option @var{print-values} determines whether names both and values, or
+just names are printed in the manner described for
+@code{-var-list-children} (@pxref{-var-list-children}).
@subsubheading Example
next prev parent reply other threads:[~2005-10-29 10:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-18 11:28 Andrew STUBBS
2005-10-19 19:58 ` Eli Zaretskii
2005-10-21 14:26 ` Andrew STUBBS
2005-10-21 14:54 ` Eli Zaretskii
2005-10-21 15:42 ` Andrew STUBBS
2005-10-21 16:42 ` Daniel Jacobowitz
2005-10-21 17:06 ` Andrew STUBBS
2005-10-21 22:04 ` Eli Zaretskii
2005-10-27 17:57 ` Andrew STUBBS
2005-10-27 19:14 ` Eli Zaretskii
2005-10-28 9:52 ` Andrew STUBBS
2005-10-28 12:49 ` Eli Zaretskii
2005-10-28 14:01 ` Andrew STUBBS
2005-10-28 17:23 ` Eli Zaretskii
2005-10-28 17:35 ` Andrew STUBBS
2005-10-29 9:52 ` Eli Zaretskii
2005-10-28 20:38 ` Daniel Jacobowitz
2005-10-29 10:32 ` Eli Zaretskii [this message]
2005-10-28 20:40 ` Daniel Jacobowitz
2005-10-28 20:47 ` 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=u64rgsjf3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=gdb@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