zsh-workers
 help / color / mirror / code / Atom feed
From: Clint Adams <clint@zsh.org>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: Zsh <zsh-workers@sunsite.dk>
Subject: possible glibc bug with buffers [was Re: 4.3.4-dev-6]
Date: Mon, 7 Jan 2008 14:44:21 -0500	[thread overview]
Message-ID: <20080107194421.GA26236@scowler.net> (raw)
In-Reply-To: <20080103170824.e3b1df78.p.w.stephenson@ntlworld.com>

On Thu, Jan 03, 2008 at 05:08:24PM +0000, Peter Stephenson wrote:
> I'm not getting that last "foo"; could there be a race somewhere, or a
> non-standard configuration option set that's doing something odd with
> file descriptors, or something nasty in the compilation tree?

My current understanding of the situation is as follows:
bash, ksh, and zsh behave normally under glibc 2.3

under glibc 2.7, ksh behaves normally

bash does this
$ echo one >/dev/full
bash: echo: write error: No space left on device
$ echo two
one
two

and zsh does this
% echo one >/dev/full
echo: write error: no space left on device
one
% echo two
two

I can't reproduce this with a simple fprintf-ing to /dev/full.


  parent reply	other threads:[~2008-01-07 19:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5951.1198159661@csr.com>
2007-12-20 20:58 ` 4.3.4-dev-6 Clint Adams
2007-12-21 18:49   ` 4.3.4-dev-6 Peter Stephenson
2007-12-22 18:09     ` 4.3.4-dev-6 Clint Adams
2008-01-03 17:08       ` 4.3.4-dev-6 Peter Stephenson
2008-01-04  4:23         ` 4.3.4-dev-6 Clint Adams
2008-01-07 19:44         ` Clint Adams [this message]
2008-01-07 20:01           ` possible glibc bug with buffers [was Re: 4.3.4-dev-6] Ismail Dönmez
2008-01-08  7:17           ` Andrey Borzenkov
2008-01-09 18:36             ` Clint Adams
2008-01-09 19:27               ` working around dietlibc or patched glibc [Re: possible glibc bug with buffers] Clint Adams

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=20080107194421.GA26236@scowler.net \
    --to=clint@zsh.org \
    --cc=p.w.stephenson@ntlworld.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).