public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lsatenstein at yahoo dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/13047] New: On 32 bit system (UBUNTU Natty) Cannot open a file of size 5GB
Date: Sun, 31 Jul 2011 01:11:00 -0000 [thread overview]
Message-ID: <bug-13047-131@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=13047
Summary: On 32 bit system (UBUNTU Natty) Cannot open a file of
size 5GB
Product: glibc
Version: unspecified
Status: NEW
Severity: critical
Priority: P2
Component: libc
AssignedTo: drepper.fsp@gmail.com
ReportedBy: lsatenstein@yahoo.com
I created a large file that I truncate to 5GB via Truncate command.
I get a NULL return from fopen("bigfile","rb"); where bigfile is 5GB exactly.
It will work with smaller files 2.5GB.
Create file with
truncate -s 5GB bigfile
The function works ok on Debian Squeeze, but not on UBUNTU. (both are 32bit
versions). I have not confirmed that it works on Fedora 32bit.
fopen() works fine with 64bit linux.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2011-07-31 1:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-31 1:11 lsatenstein at yahoo dot com [this message]
2011-07-31 1:12 ` [Bug libc/13047] " lsatenstein at yahoo dot com
2011-07-31 18:58 ` aj at suse dot de
2011-07-31 23:24 ` lsatenstein at yahoo dot com
2011-08-01 7:22 ` aj at suse dot de
2011-08-07 17:57 ` bugdal at aerifal dot cx
2012-05-14 4:22 ` bugdal at aerifal dot cx
2012-05-14 10:55 ` joseph at codesourcery dot com
2014-06-13 14:36 ` [Bug libc/13047] Make 64-bit off_t the default on i386 and others fweimer at redhat dot com
2014-06-13 14:37 ` fweimer at redhat dot com
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=bug-13047-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).