zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <Peter.Stephenson@csr.com>
To: <zsh-workers@zsh.org>
Subject: Re: Zsh 4.3.12: subshell in midnight commander:  precmd: 15: bad file descriptor
Date: Mon, 18 Jul 2011 17:01:24 +0100	[thread overview]
Message-ID: <20110718170124.20d6cae4@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <110718085234.ZM13898@torch.brasslantern.com>

On Mon, 18 Jul 2011 08:52:34 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> Hrm.  So why does it work when starting 4.3.12 from 4.3.9?  How is 11
> getting to be <= max_zsh_fd inside 4.3.12 that case, whereas it is not
> when the outer shell is 4.3.12?

See what lsof says.  I suspect 4.3.9 is leaving open its SHTTY, since
setting FD_CLOEXEC on that is one of the changes I noted.  That would be
fd 12, so 11 is <max_zsh_fd.

> It prevents the specific error in question, but there are also going to be
> changes needed here:
> 
>    2975                         fn->fd1 = (int)getintvalue(v);
>    2976                         if (errflag)
>    2977                             bad = 1;
> *  2978                         else if (fn->fd1 > max_zsh_fd)
>    2979                             bad = 3;
>    2980                         else if (fn->fd1 >= 10 &&
>    2981                                  fdtable[fn->fd1] == FDT_INTERNAL)
>    2982                             bad = 4;

Hmm... that's saying we're closing an fd with {foo}>&- syntax that
we don't know about in the first place.  Do we just try to close it and
report an error closing an unknown fd if that fails?

> And what's going to happen when max_zsh_fd does in fact become greater
> than the "unknown" descriptor?  Any problems with fdtable[x] having
> bogus data?  Isn't closem() going to attempt to close a descriptor
> that it shouldn't?

I think that works, since we handle unknown fd's marked as unknown as
best we can.  In fact, I think you may just have tested it.

-- 
Peter Stephenson <pws@csr.com>            Software Engineer
Tel: +44 (0)1223 692070                   Cambridge Silicon Radio Limited
Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, UK


Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom
More information can be found at www.csr.com. Follow CSR on Twitter at http://twitter.com/CSR_PLC and read our blog at www.csr.com/blog


  reply	other threads:[~2011-07-18 16:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-18  8:26 Pavel Reznicek
2011-07-18  9:07 ` Peter Stephenson
2011-07-18 10:04   ` Pavel Reznicek
2011-07-18 14:07     ` Bart Schaefer
2011-07-18 14:45     ` Bart Schaefer
2011-07-18 15:24       ` Peter Stephenson
2011-07-18 15:52         ` Bart Schaefer
2011-07-18 16:01           ` Peter Stephenson [this message]
2011-07-18 16:26             ` Bart Schaefer
2011-07-19  9:47               ` Peter Stephenson
2011-07-19  9:52           ` Peter Stephenson
2011-07-19 14:28             ` Bart Schaefer
2011-07-18 14:13 ` Peter Stephenson
2011-10-02 19:00   ` Pavel Reznicek

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=20110718170124.20d6cae4@pwslap01u.europe.root.pri \
    --to=peter.stephenson@csr.com \
    --cc=zsh-workers@zsh.org \
    /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).