[Tcl-bugs] [ tcl-Bugs-1287638 ] Missing O_LARGEFILE flag?

[SourceForge.net <no...@so...>]

Bugs item #1287638, was opened at 2005-09-11 04:03
Message generated for change (Comment added) made by roboxhack
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110894&aid=1287638&group_id=10894

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: 36. File System
Group: current: 8.4.11
Status: Open
Resolution: None
Priority: 8
Submitted By: Palan (roboxhack)
Assigned to: Donal K. Fellows (dkf)
Summary: Missing O_LARGEFILE flag?

Initial Comment:
TCL does not support writing more than 2 GB to files

In generic/tclIOUtil.c

Function: TclGetOpenMode

For opening new files, the O_LARGEFILE flag should be
added to support >2GB files:

	    case 'w':
		mode = O_WRONLY|O_CREAT|O_TRUNC;

should be

	#define O_LARGEFILE     0100000
 .....
	 case 'w':
                mode =
O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE;


The same needs to be done for appending and other file
access modes.


----------------------------------------------------------------------

>Comment By: Palan (roboxhack)
Date: 2005-09-14 17:08

Message:
Logged In: YES 
user_id=1342738

Platform is RHEL v3. 

I noticed the problem while using ns2 network simulator,
simulations above 2 GB generated the SIGXFSZ signal. ns2
uses TCL to set up the simulation files, the file handle
being used in TCL suffers from the above problem. 

Fixing the TCL code as above solved the problem and
simulations larger than 2 GB worked. 


----------------------------------------------------------------------

Comment By: Donal K. Fellows (dkf)
Date: 2005-09-12 03:54

Message:
Logged In: YES 
user_id=79902

Tcl actually uses open64() where available, which is
documented to behave as open() with the O_LARGEFILE flag. At
least on Solaris and AIX. Can't find any docs on Linux or
SGI (though both support it) and the ancient FreeBSD box
I've got access to doesn't seem to support either open64 or
O_LARGEFILE.

If you can actually exhibit a failure (as opposed to "you've
looked at the source and can't find the flag") please
describe exactly what platform you're on.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110894&aid=1287638&group_id=10894