Re: error on TTY read: no such file or directory

[Peter Stephenson <pws@xxxxxxx>]

Bart Schaefer wrote:
> I'd be suspicious that the kernel is expecting a 64-bit value as the
> third argument to read() and is getting only a 32-bit value -- but in
> that case I'd expect strace to show the whole 64 bits so that we'd be
> able to tell how many bytes read() really was looking for; and that
> would leave the question of where the other 1024 bytes came from, and
> why stuffing 1025 bytes through the address of a single character on
> the stack doesn't cause a more serious meltdown ...

Or could it be the other way around and _LARGEFILE_SOURCE and the
corresponding definitions, such as open64, aren't being handled correctly?
It's certainly at least partially in effect because of the stat64.

May be a complete red herring.

-- 
Peter Stephenson <pws@xxxxxxx>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 392070


**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential 
and/or privileged material. 
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is 
prohibited.  
If you received this in error, please contact the sender and 
delete the material from any computer.
**********************************************************************