Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Bug#266031: zsh: still segfaults occasionally on sid
- X-seq: zsh-workers 23790
- From: Niko Tyni <ntyni@xxxxxx>
- To: zsh-workers@xxxxxxxxxx, 266031-forwarded@xxxxxxxxxxxxxxx
- Subject: Re: Bug#266031: zsh: still segfaults occasionally on sid
- Date: Wed, 22 Aug 2007 07:55:54 +0300
- In-reply-to: <20070821225301.GB31741@xxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20070821191245.GA29403@xxxxxxxxxxxxxxxxxxxx> <20070821225301.GB31741@xxxxxxxxxxx>
On Tue, Aug 21, 2007 at 06:53:01PM -0400, Clint Adams wrote:
> On Tue, Aug 21, 2007 at 10:12:45PM +0300, Niko Tyni wrote:
> > I'm seeing this bug maybe once or twice a day on amd64/sid (and
> > on etch too.) I'm also using the vi bindings, and the bug always
> > hits me when browsing or searching history, usually when I press 'k'
> > (up-line-or-history) in the vicmd mode. I think the history has to grow
> > long enough first or something, it never seems to happen early in the
> > terminal session. I have tried to find a way to reproduce the crash
> > reliably, but no luck yet.
> >
> > Here's the gdb backtrace and the message displayed on the terminal after
> > the latest crash. Please let me know if I can provide more information.
>
> Which history-related options are you setopt-ing?
Just 'unsetopt appendhistory', I think.
% setopt
noalwayslastprompt
noappendhistory
noautomenu
noautoremoveslash
nobeep
interactive
login
monitor
nonomatch
shinstdin
zle
> What are the values of $HISTSIZE and $SAVEHIST ?
% echo $HISTSIZE
30
% echo $SAVEHIST
0
> What kind of filesystem is your history file stored on/over?
There's no saved history due to SAVEHIST=0, as far as I understand.
The home directory is on ext3 if that matters anyway.
Cheers,
--
Niko Tyni ntyni@xxxxxx
Messages sorted by:
Reverse Date,
Date,
Thread,
Author