Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: gdb-patches@sources.redhat.com,
	Eli Zaretskii <eliz@is.elta.co.il>,
	Corinna Vinschen <vinschen@redhat.com>
Subject: Re: [RFA]: File-I/O patch, Documentation
Date: Tue, 04 Mar 2003 18:53:00 -0000	[thread overview]
Message-ID: <3E64F632.4070005@redhat.com> (raw)
In-Reply-To: <20030303121249.GM1193@cygbert.vinschen.de>

[added Eli]

> On Sat, Mar 01, 2003 at 09:58:44PM -0500, Andrew Cagney wrote:
> 
>> Well the texinfo.  I read the reference as a reference to something 
>> completly separate.
>> 
>> Can you please expand the paragraph to reference: Protocol specific 
>> representation of datatypes.
> 
> 
> Uhm... sorry but is it possible that you didn't read the texinfo file
> created by my patch send the week before but instead the one from
> December?  I just looked through the doc and I was a bit surprised
> to see that there isn't any reference to B.1 but instead there's
> already a "(see @ref{Integral datatypes}, for details)" in it.

Yes.  I'm having a `bad hair' day :-(

> I've attached the new version of my patch with the following changes:
> 
> - Using M packets for memory transfer is redefined so that the target
>   should expect M or X packets.  The current implementation (my patch)
>   uses only X packets so far.  I forgot that in the original document.
> 
> - The "Integral datatypes" chapter contains a hint that these datatypes
>   are passed as big endian when part of a memory transfer of a compound
>   type.
> 
> - The "Integral datatypes" chapter defines time_t as seconds since Epoch.
> 
> - A new "File-I/O Examples" chapter.

I just tried to build a pdf file using this patch and it died with:

(/usr/share/texmf/pdftex/plain/misc/pdfcolor.tex) fonts, page headings,
tables, conditionals, indexing, sectioning, toc, environments, defuns, 
macros,
cross references, (/usr/share/texmf/tex/plain/dvips/epsf.tex) localization,
and turning on texinfo input format.) (./gdb.aux
! Missing @endcsname inserted.
<to be read again>
                    @
<argument> The `F@
                    request packet-title
@xrdef ...@endgroup @expandafter @gdef @csname X#1
                                                   @endcsname
l.862 'xrdef {The `F' request packet-title}
                                            {The \code {F} request packet}
?

Changing the line:

	@subsection The @code{F} request packet

(and a second very similar in a similar way) to:

	@subsection The `F' request packet

fixed the problem.  This has me totally puzzled since other @subsection 
lines use @..{} and work fine.

Eli?

Andrew

PS: pdftex on a RHAT 7.2 system.



  reply	other threads:[~2003-03-04 18:53 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-21  1:04 Corinna Vinschen
2002-11-21  1:22 ` Corinna Vinschen
2002-11-23  3:04   ` Eli Zaretskii
2002-11-23  3:02 ` Eli Zaretskii
2002-11-23  8:12   ` Andrew Cagney
2002-11-25  2:52   ` Corinna Vinschen
2002-11-25 11:01     ` Eli Zaretskii
2002-11-26  6:07       ` Corinna Vinschen
2002-11-26 10:02         ` Eli Zaretskii
2002-11-27  9:08           ` Corinna Vinschen
2003-02-26 23:20 ` Andrew Cagney
2003-02-27  8:37   ` Corinna Vinschen
2003-02-27 23:05     ` Andrew Cagney
2003-02-28  8:33       ` Corinna Vinschen
2003-02-28 15:25         ` Daniel Jacobowitz
2003-02-28 15:49           ` Corinna Vinschen
2003-02-28 16:37             ` Daniel Jacobowitz
2003-02-28 15:27         ` Andrew Cagney
2003-02-28 15:47           ` Corinna Vinschen
2003-03-02  3:03             ` Andrew Cagney
2003-03-03 12:12               ` Corinna Vinschen
2003-03-04 18:53                 ` Andrew Cagney [this message]
2003-03-04 19:46                   ` Eli Zaretskii
2003-03-06 21:19                     ` Andrew Cagney
2003-03-06 21:26                 ` Andrew Cagney
2003-03-07 14:29                   ` Corinna Vinschen
2003-03-07 14:55                     ` Andrew Cagney
2003-03-01 12:36     ` Eli Zaretskii
2003-03-01 15:43       ` Andrew Cagney

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=3E64F632.4070005@redhat.com \
    --to=ac131313@redhat.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    --cc=vinschen@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