• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

2GB File Size Limit in Linux??

A

Armitage

Banned
Sure back in the bad old 2.2 days! But not with a 2.4.18 kernel!

I've got a simple C++ sim going that generates a ton of data. When the ASCII output file hit the 2GB mark, it died with a message "File size limit exceeded".
What's wierd is that I can use dd to create a file > 2GB on the same partition, so it seems like it must be a C++ limitation, not a filesystem limitation. But I know I've used C/C++ programs to generate > 2GB files in the past (on a different machine, different kerner, distro, etc.). Any ideas??

Relavent information:
RedHat 8.0 w/ 2.4.18
ext3 on software RAID1
gcc v3.2.7

I'm writing to a standard fstream object.

 
ugg ... gcc bug 🙁

Linkage

Kind of disturbing to see it marked "critical" but unassigned after > 1 month. It seems to be a relatively recent bug and also doesn't affect stdio which explains why my other program worked (didn't use iostream).
 
Aha, its not assigned because its a duplicate of this, where work seems to have stalled early in Feb. :brokenheart:

Don't mind me ... just talking to myself here. 😱
 
I know for a fact that it worked with RedHat GCC from 7.2 (AKA 2.96) and with the 2.95 versions. I don't know about the 3.0, I didn't start using 3.* until 3.1
 
Originally posted by: ergeorge
I know for a fact that it worked with RedHat GCC from 7.2 (AKA 2.96) and with the 2.95 versions. I don't know about the 3.0, I didn't start using 3.* until 3.1
Click to expand...

Well, maybe there is a way to be able to use both 2.95 and 3.x on the same system.
 
Yea, I've done that before ... don't recall why. It's something of a PITA
For now, I've changed the io in the affected app from iostream to stdio ... which was easy for this one because it was a trivial program which just happened to generate an obscene amount of output 😀
But another of our major programs may be coming online again soon, and I know for certain this breaks it 🙁, although there may be some workarounds.

If my PR gets approved, we'll be getting a new xeon based cluster soon, and the intel compiler suite. 😀😀 I'll have to see if the intel compilers use the gcc libstdc++, or provide their own.

edit: Actually, RedHat 7.* shipped with both a 2.9* GCC and a 3.* GCC ... so it's definitely possible to have more then one on a system.
 
Alot of people haven't moved to the 3.* releases yet. For one thing, it breaks alot of broken code that older versions accepted, and early releases were VERY slow compiling.
I was happy with it up until this mess.
 
Originally posted by: ergeorge
update ... target to fix this is GCC 3.4 "sometime this year" 🙁
Click to expand...
Heh, that seems like a pretty serious bug; I wish they would fix it soon, but the chances of any Open-Source software coming out "on time" are virtually nil. :disgust:

<-- is going to learn C++ and this bug would probably affect a program he will be writing. :frown:
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top