From: Niko Tyni <ntyni@iki.fi>
To: zsh-workers@sunsite.dk, 266031-forwarded@bugs.debian.org
Subject: Re: Bug#266031: zsh: still segfaults occasionally on sid
Date: Wed, 22 Aug 2007 07:55:54 +0300 [thread overview]
Message-ID: <20070822045554.GA32386@rispa.it.helsinki.fi> (raw)
In-Reply-To: <20070821225301.GB31741@scowler.net>
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@iki.fi
prev parent reply other threads:[~2007-08-22 6:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070821191245.GA29403@rispa.it.helsinki.fi>
2007-08-21 22:53 ` Clint Adams
2007-08-22 4:55 ` Niko Tyni [this message]
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=20070822045554.GA32386@rispa.it.helsinki.fi \
--to=ntyni@iki.fi \
--cc=266031-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).