zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk, 251378-forwarded@bugs.debian.org
Subject: Re: Bug#251378: zsh: segfaults when globing includes too many files
Date: Wed, 07 Jul 2004 12:01:34 +0100	[thread overview]
Message-ID: <200407071101.i67B1Ygr024643@news01.csr.com> (raw)
In-Reply-To: "Clint Adams"'s message of "Tue, 06 Jul 2004 14:59:26 EDT." <20040706185926.GA14980@scowler.net>

Clint Adams wrote:
> I can't reproduce this yet, but some people are experiencing segfaults
> when globbing in /usr/share/doc.  The source shown below includes 19920.
> This also happens with HEAD, I think.

So this happens with both 4.2.0 and the latest, and therefore isn't
(directly) related to the mmap reorganisation of heap allocation?

Is it possible a memory allocator is returning 0?  It could be another
case where the shell is trying to allocate way too much memory, not
getting it, and not handling the failure gracefully.

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


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************


  parent reply	other threads:[~2004-07-07 11:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040528125647.GA21000@scowler.net>
     [not found] ` <20040528131425.GC2289@via.ecp.fr>
     [not found]   ` <20040528135026.GA21637@scowler.net>
     [not found]     ` <20040528135729.GD2289@via.ecp.fr>
     [not found]       ` <20040528141431.GA30024@scowler.net>
     [not found]         ` <20040528142505.GE2289@via.ecp.fr>
     [not found]           ` <20040528174021.GA5975@scowler.net>
     [not found]             ` <20040528190653.GA2661@via.ecp.fr>
     [not found]               ` <20040706181235.GA32727@scowler.net>
     [not found]                 ` <20040706184752.GC1881@alcor.net>
2004-07-06 18:59                   ` Clint Adams
2004-07-06 19:22                     ` Clint Adams
2004-07-13 11:06                       ` Peter Stephenson
2004-07-16 17:56                         ` Clint Adams
2004-07-16 19:46                           ` Clint Adams
2004-07-17 19:06                             ` Peter Stephenson
2004-07-17 19:20                           ` PATCH: " Peter Stephenson
2004-07-07 11:01                     ` Peter Stephenson [this message]
2004-07-07 12:36                       ` 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=200407071101.i67B1Ygr024643@news01.csr.com \
    --to=pws@csr.com \
    --cc=251378-forwarded@bugs.debian.org \
    --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).