Re: vanishing history

[Adam Spiers <adam@xxxxxxxxxx>]

Adam Spiers (adam@xxxxxxxxxx) 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