zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk
Subject: Re: Util/helpfiles - problem with provided example
Date: Wed, 28 Jul 2004 11:21:20 +0100	[thread overview]
Message-ID: <200407281021.i6SALKHN026997@news01.csr.com> (raw)
In-Reply-To: "Peter Stephenson"'s message of "Wed, 28 Jul 2004 11:01:15 BST." <200407281001.i6SA1FvF026186@news01.csr.com>

Peter Stephenson wrote:
> Michael Prokop wrote:
> > man () {
> >        man $1                                     # this is the original
> >   }
> > $ man zsh
> 
> > Segmentation fault
> 
> This isn't very nice.  Should we turn on --enable-max-function-depth by
> default?  The default for --enable-max-function-depth=yes is 4096 which
> isn't going to hurt most people.  Or should we make it configurable
> internally with a sensible default?

More investigation reveals a further problem.  There's an arbitrary
debugging check when unreferencing the function that it hasn't been
referenced more than 256 times.  This needs to be the function depth if
that is defined plus 1 (to allow for the original function struture).
I've added a few on for fuzz.  Presumably the test is meaningless if
there is no function depth limit.

If you try this with a the default function depth limit, it's
interesting to note that the error message is printed almost straight
away, while the prompt takes a while to return.  I wonder if freeing
things up is slower than necessary?

Index: Src/parse.c
===================================================================
RCS file: /cvsroot/zsh/zsh/Src/parse.c,v
retrieving revision 1.46
diff -u -r1.46 parse.c
--- Src/parse.c	28 Jun 2004 15:38:14 -0000	1.46
+++ Src/parse.c	28 Jul 2004 10:18:28 -0000
@@ -2168,7 +2168,10 @@
 	/* paranoia */
 	DPUTS(p->nref > 0 && (p->flags & EF_HEAP), "Heap EPROG has nref > 0");
 	DPUTS(p->nref < 0 && !(p->flags & EF_HEAP), "Real EPROG has nref < 0");
-	DPUTS(p->nref < -1 || p->nref > 256, "Uninitialised EPROG nref");
+	DPUTS(p->nref < -1, "Uninitialised EPROG nref");
+#ifdef MAX_FUNCTION_DEPTH
+	DPUTS(p->nref > MAX_FUNCTION_DEPTH + 10, "Overlarge EPROG nref");
+#endif
 	if (p->nref > 0 && !--p->nref) {
 	    for (i = p->npats, pp = p->pats; i--; pp++)
 		freepatprog(*pp);

-- 
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
**********************************************************************


  reply	other threads:[~2004-07-28 10:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-26 22:30 Michael Prokop
2004-07-28 10:01 ` Peter Stephenson
2004-07-28 10:21   ` Peter Stephenson [this message]
2004-07-29 15:40   ` Peter Stephenson

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=200407281021.i6SALKHN026997@news01.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).