From: Adam Spiers <adam@spiers.net>
To: zsh workers mailing list <zsh-workers@sunsite.auc.dk>
Subject: Re: vanishing history
Date: Mon, 18 Feb 2002 18:15:05 +0000 [thread overview]
Message-ID: <20020218181505.A28159@corelli.new.ox.ac.uk> (raw)
In-Reply-To: <20020218181021.A27877@corelli.new.ox.ac.uk>; from adam@spiers.net on Mon, Feb 18, 2002 at 06:10:21PM +0000
Adam Spiers (adam@spiers.net) wrote:
> Thanks for that. I've found a way to reproduce the bug, and this
> patch (or at least, the combination of all cvs commits over the last
> few weeks) makes zsh core dump when I try that way, which is to simply
> type ^X?, which is bound to _complete_debug. This somehow manages to
> reset the history file to almost empty. I've tracked it as far as the
> inc_append_history option, which disabling stops the core dump.
> Beyond that I'm out of my depth.
Apologies, I forgot to include a stack trace.
#0 0x0807931f in savehistfile (fn=0x80ef1c0 "/nfs-home/adams/.zshhistory",
err=0, writeflags=32771) at hist.c:2050
2050 for (; *t; t++) {
(gdb) bt
#0 0x0807931f in savehistfile (fn=0x80ef1c0 "/nfs-home/adams/.zshhistory",
err=0, writeflags=32771) at hist.c:2050
#1 0x08076f52 in hend (prog=0x0) at hist.c:1154
#2 0x08079ff8 in loop (toplevel=1, justonce=0) at init.c:129
#3 0x0807c849 in zsh_main (argc=1, argv=0xbffff374) at init.c:1214
#4 0x080518f0 in main (argc=1, argv=0xbffff374) at ./main.c:37
#5 0x4008f6f7 in __libc_start_main (main=0x80518e0 <main>, argc=1,
ubp_av=0xbffff374, init=0x8050e08 <_init>, fini=0x80bd89c <_fini>,
rtld_fini=0x4000dcd4 <_dl_fini>, stack_end=0xbffff36c)
at ../sysdeps/generic/libc-start.c:129
next prev parent reply other threads:[~2002-02-18 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011128161905.A9726@corelli.new.ox.ac.uk>
[not found] ` <Pine.LNX.4.33L2.0202160123440.1473-100000@phong.blorf.net>
2002-02-18 18:10 ` Adam Spiers
2002-02-18 18:15 ` Adam Spiers [this message]
2002-02-18 19:31 ` Wayne Davison
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=20020218181505.A28159@corelli.new.ox.ac.uk \
--to=adam@spiers.net \
--cc=zsh-workers@sunsite.auc.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).