Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Segfaulting script
- X-seq: zsh-workers 22497
- From: Frank Terbeck <frank.terbeck@xxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: Segfaulting script
- Date: Sat, 17 Jun 2006 20:14:17 +0200
- In-reply-to: <060617101117.ZM32743@xxxxxxxxxxxxxxxxxxxxxx>
- Mail-followup-to: zsh-workers@xxxxxxxxxx
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- Operating-system: Linux 2.6.16.16 i686
- References: <20060613231505.GA23239@xxxxxxxxxxxx> <20060616110319.GB2780@xxxxxxxxxxxxxxx> <060617101117.ZM32743@xxxxxxxxxxxxxxxxxxxxxx>
Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>:
> On Jun 16, 1:03pm, Frank Terbeck wrote:
> }
> } I don't know if this is the same bug, but it might be closely related:
> }
> } [snip]
> } % zsh -f
> } % testfunc() { local foo=() ; local bar }
>
> You can't assign values to an array in a "local" statement. When zsh
> parses the above, it's seeing
[...]
Yes, I know that the assignment does not make sense.
> which (of course) is a recursive call to the newly-created function
> "local". I don't get a segfault with 4.3.2-dev-1, I get an error:
>
> zsh% local
> local:10: maximum nested function level reached
> zsh%
Okay.
> The fact that "compinit" or a completion comes next is a red herring; any
> function that used "local" would cause the error.
Thanks for clarifying that.
> My guess would be that you get a segfault when the compile-time setting
> of the maximum function depth is large enough that you run out of memory
> before the limit is hit. There's not a whole lot we can do about that.
Hm, definitely no nice, but I trust your judgement.
Regards, Frank
Messages sorted by:
Reverse Date,
Date,
Thread,
Author