Kuberan Naganathan added the comment:
yes. i noticed problem on solaris on the /proc//as file which usually
has mapped regions beyond 2^63 in most process files
On Jul 22, 2011 4:35 PM, "Charles-François Natali"
wrote:
>
> Charles-François Natali added the comment:
&g
Kuberan Naganathan added the comment:
Hi. I'm unable ( or have to jump through lots of hoops ) to submit this patch
myself for regulatory reasons. Can someone else submit this please? Thanks.
--
___
Python tracker
<http://bugs.py
Kuberan Naganathan added the comment:
Hi. I can submit a patch for the first part. Should I submit on this issue
tracker item?
--
___
Python tracker
<http://bugs.python.org/issue12
Kuberan Naganathan added the comment:
I did some testing on this. Solaris seems to treat files as a large
circular buffer of size 2^64 with respect to seeks in the /proc file system
address space file. No error results with seeks of greater than 2^63 with
any of SEEK_SET, SEEK_CUR, SEEK_END
Kuberan Naganathan added the comment:
Im most familiar with solaris. Atleast on solaris lseek interprets its
signed arg as the unsigned value with the same bit pattern. I cannot be
certain that this is common across other operating systems.
On Jul 13, 2011 8:09 AM, "Antoine Pitrou&qu
Kuberan Naganathan added the comment:
In addition I would like the posix_lseek function to accept a value larger than
2^63 as a seek offset. Currently I seem to need to seek multiple times within
a file to achieve an offset larger than 2^63 ( assuming the return type check
on the return
New submission from Kuberan Naganathan :
The lseek function can legitimately return a code less then zero ( except for
-1 ) when seeking beyond an offset of 2^63. This behavior should be supported
in order to permit the python interpreter to seek in files with valid data at
locations greater
