Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Bart Veer <bartv@ecoscentric.com>
To: gdb-patches@sourceware.org
Subject: minor doc fix
Date: Wed, 30 Jul 2008 15:55:00 -0000	[thread overview]
Message-ID: <pnbq0ffjuk.fsf@delenn.bartv.net> (raw)

Current docs for the remote protocol file I/O extension state that a
struct timeval is 8 bytes. It is actually 12, a 4-byte time_t tv_sec
and an 8-byte long tv_usec. It is not clear why tv_usec was made a
long rather than an int, but that is what has been implemented in
remote_fileio_to_fio_timeval() and hence what current server
implementations expect.

Bart

2008-07-30  Bart Veer  <bartv@ecoscentric.com>

	* gdb.texinfo: gettimeofday() involves a 12-byte transfer, not 8
	bytes.

Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.509
diff -u -p -r1.509 gdb.texinfo
--- gdb.texinfo	18 Jul 2008 20:55:33 -0000	1.509
+++ gdb.texinfo	30 Jul 2008 14:55:06 -0000
@@ -26636,7 +26636,7 @@ struct timeval @{
 
 The integral datatypes conform to the definitions given in the
 appropriate section (see @ref{Integral Datatypes}, for details) so this
-structure is of size 8 bytes.
+structure is of size 12 bytes.
 
 @node Constants
 @subsection Constants
	


             reply	other threads:[~2008-07-30 15:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-30 15:55 Bart Veer [this message]
2008-07-30 17:55 ` Eli Zaretskii
2008-07-30 18:17   ` Bart Veer
2008-07-30 18:34     ` Eli Zaretskii
2008-07-30 18:49       ` Daniel Jacobowitz
2008-07-30 19:08         ` Eli Zaretskii
2008-07-30 19:15           ` Daniel Jacobowitz
2008-07-30 20:28       ` Bart Veer

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=pnbq0ffjuk.fsf@delenn.bartv.net \
    --to=bartv@ecoscentric.com \
    --cc=gdb-patches@sourceware.org \
    /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