Re: Should 32-bit apps work with a 64-bit kernel?
Ron Johnson <ron.l.johnson@cox.net> writes:
> On 02/09/2009 08:04 AM, Ron Johnson wrote:
>> On 02/09/2009 12:28 AM, Martin Langhoff wrote:
>>> On Mon, Feb 9, 2009 at 2:19 PM, Ben Hutchings <ben@decadent.org.uk>
>>> wrote:
>>>> If jed can deal with files that large, sure. But if it expects to be
>>>> able to load the entire file into memory - as most text editors do -
>>>> stat() will be only the first of its problems.
>>>
>>> Old vi was able to work with files larger than available RAM. I wonder
>>> if any modern text editor today can still handle that.
>>
>> I've got a 23GB text file that vim 7.2.079-1 just won't "see".
>>
>> more(1) processes it, file(1) processes it, but vim displays an
>> empty screen with "[New File]" at the bottom.
>
> Bug #514617.
>
> stat64("ACCOUNT_TOLL_V20_200408.UNL", {st_mode=S_IFREG|0640,
> st_size=23726916643, ...}) = 0
> stat64("ACCOUNT_TOLL_V20_200408.UNL", {st_mode=S_IFREG|0640,
> st_size=23726916643, ...}) = 0
> access("ACCOUNT_TOLL_V20_200408.UNL", W_OK) = 0
> open("ACCOUNT_TOLL_V20_200408.UNL", O_RDONLY) = -1 EOVERFLOW (Value
> too large for defined data type)
> readlink("ACCOUNT_TOLL_V20_200408.UNL", 0xfff19c4c, 4095) = -1
> EINVAL (Invalid argument)
>
Maybe we need a mass bug filing for programs not using 64bit file
offsets.
Anyone up for hacking libc to always fail on the 32bit wrappers for
seek, stat, ...?
MfG
Goswin
Reply to: