Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: Still able to reproduce history crash (3.0.4)

X-seq: zsh-workers 3408
From: Zoltan Hidvegi <hzoli@xxxxxxxxxxxxxxx>
To: schaefer@xxxxxxxxxxxxxxxx (Bart Schaefer)
Subject: Re: Still able to reproduce history crash (3.0.4)
Date: Sun, 3 Aug 1997 21:01:51 -0400 (EDT)
Cc: zsh-workers@xxxxxxxxxxxxxxx
In-reply-to: <970803165508.ZM12879@xxxxxxxxxxxxxxxxxxxxxxx> from Bart Schaefer at "Aug 3, 97 04:55:08 pm"

> And still unable to get a backtrace.
> 
> Easiest way to reproduce is to start zsh -f, then do:
> 
> HISTSIZE=0
> HISTSIZE=5
> 
> and then execute at least five commands.  Appears to dump in malloc(), but
> as the stack is complete garbage there's no way to be sure.  I've enabled
> all the debug and mem-debug options but there's not even a hint of an error
> until the gooey kablooey.

I'll try to look at it, but right now, I'm busy rewriting paramsubst() to
clean up the mess around rc_expand_param and the (e) flag.  This turned
out to be a much more difficult problem than I first thought, but
hopefully the final code will be a bit simpler than the current one.

Zoltan

References:
- Still able to reproduce history crash (3.0.4)
  - From: Bart Schaefer

Messages sorted by: Reverse Date, Date, Thread, Author