From: Roland McGrath <roland@redhat.com>
To: GNU libc hackers <libc-hacker@sources.redhat.com>
Subject: EOVERFLOW for ftell, ftello, fgetpos?
Date: Wed, 23 Oct 2002 16:58:00 -0000 [thread overview]
Message-ID: <200210232151.g9NLpCA28795@magilla.sf.frob.com> (raw)
Aren't ftell, ftello, and fgetpos supposed to diagnose EOVERFLOW?
(A program could fopen, fread pieces totalling >4GB, and then call ftell.)
Right now these functions all just truncate the result of _IO_seekoff to 32
bits (and treat 4294967295 as an error). Unless someone tells me why I'm
wrong about thinking this is a bug, I will fix them to detect overflow.
reply other threads:[~2002-10-23 21:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200210232151.g9NLpCA28795@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=libc-hacker@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).