From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: error on TTY read: no such file or directory
Date: Mon, 01 Oct 2001 10:31:43 +0100 [thread overview]
Message-ID: <6926.1001928703@csr.com> (raw)
In-Reply-To: "Bart Schaefer"'s message of "Sun, 30 Sep 2001 02:23:16 -0000." <1010930022316.ZM20422@candle.brasslantern.com>
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@csr.com> 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.
**********************************************************************
next prev parent reply other threads:[~2001-10-01 9:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010910200737.A6256@hithaeglir.net>
[not found] ` <001f01c13abb$6997dca0$21c9ca95@mow.siemens.ru>
[not found] ` <20010911084904.A11501@hithaeglir.net>
[not found] ` <1010911140155.ZM24429@candle.brasslantern.com>
[not found] ` <20010928121347.B16561@hithaeglir.net>
[not found] ` <3BB56D03.2000300@mow.siemens.ru>
[not found] ` <20010929034953.E16561@hithaeglir.net>
[not found] ` <3BB62E93.10802@mow.siemens.ru>
[not found] ` <20010929170811.G16561@hithaeglir.net>
2001-09-29 21:28 ` Borsenkow Andrej
[not found] ` <20010929173848.H16561@hithaeglir.net>
2001-09-29 21:56 ` Borsenkow Andrej
2001-09-29 22:11 ` lordzork
2001-09-29 22:19 ` Borsenkow Andrej
2001-09-29 22:31 ` lordzork
2001-09-29 22:39 ` Bart Schaefer
2001-09-30 0:24 ` lordzork
2001-09-30 1:20 ` Zefram
2001-09-30 2:23 ` Bart Schaefer
2001-10-01 9:31 ` Peter Stephenson [this message]
2001-09-30 1:24 ` Bart Schaefer
2001-09-30 1:34 ` lordzork
2001-09-30 6:25 ` Borsenkow Andrej
2001-09-30 11:23 ` lordzork
2001-09-30 11:48 ` lordzork
2001-09-30 12:38 ` Zefram
2001-09-30 15:44 ` Borsenkow Andrej
2001-09-30 16:22 ` Bart Schaefer
2001-09-30 16:40 ` Borsenkow Andrej
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6926.1001928703@csr.com \
--to=pws@csr.com \
--cc=zsh-workers@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).