From: "Thomas Köhler" <jean-luc@picard.franken.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: zsh-3.1.9-dev-6 crashes occassionally
Date: Mon, 23 Oct 2000 17:12:14 +0200 [thread overview]
Message-ID: <20001023171214.B15065@picard.franken.de> (raw)
In-Reply-To: <200010231304.PAA22181@beta.informatik.hu-berlin.de>; from wischnow@informatik.hu-berlin.de on Mon, Oct 23, 2000 at 03:04:00PM +0200
[-- Attachment #1: Type: text/plain, Size: 1879 bytes --]
On Mon, Oct 23, 2000 at 03:04:00PM +0200,
Sven Wischnowsky <wischnow@informatik.hu-berlin.de> wrote:
>
> Thomas Koehler wrote:
>
> > ...
> >
> > #0 0x401011cb in free () from /lib/libc.so.6
> > (gdb) bt
> > #0 0x401011cb in free () from /lib/libc.so.6
> > #1 0x40101053 in free () from /lib/libc.so.6
> > #2 0x807613e in zsfree ()
> > #3 0x80925e3 in freearray ()
> > #4 0x807cd66 in arrsetfn ()
> > #5 0x807cc82 in stdunsetfn ()
> > #6 0x807cb5a in unsetparam_pm ()
> > #7 0x807de6d in endparamscope ()
> > #8 0x8065a49 in scanhashtable ()
> > #9 0x807dd8f in endparamscope ()
> > #10 0x8060304 in runshfunc ()
> > #11 0x4021f682 in comp_setunset () from /usr/lib/zsh/3.1.9-dev-6/zsh/comple=
> > te.so
>
> Hm. This seems to suggest that there is some trouble with unsetting
> the special completion parameters. $words, I guess. We already fixed
> some problems with it some time ago, but that was before 3.1.9.
>
> I'll try to stare some more at the code, but can't promise anything.
Could my whole .zshrc be of any help?
~> wc -l .zshrc
625 .zshrc
Perhaps it's only triggered by one of my settings?
> Do you have any remembrance of what you tried to complete when it crashed?
Well, as zsh dumped core in /scratch2/mp3 while completing, it was
either "cd" completing directory names or "mpg123" completing file and
directory names, can't say for sure now.
But I think zsh also crashed for other things (hostname completion for
ssh or something)... Can't really say for sure at the moment.
> Bye
> Sven
CU,
Thomas
--
Thomas Köhler Email: jean-luc@picard.franken.de | LCARS - Linux
<>< WWW: http://jeanluc-picard.de | for Computers
IRC: jeanluc | on All Real
PGP public key available from Homepage! | Starships
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2000-10-23 15:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-23 13:04 Sven Wischnowsky
2000-10-23 15:12 ` Thomas Köhler [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-08 10:54 Sven Wischnowsky
2000-11-08 9:41 Sven Wischnowsky
2000-11-08 10:33 ` Thomas Köhler
2000-11-01 9:41 Sven Wischnowsky
2000-11-03 15:42 ` Bart Schaefer
2000-11-05 17:55 ` Thomas Köhler
2000-10-31 15:42 Sven Wischnowsky
2000-10-31 13:19 Sven Wischnowsky
2000-10-31 13:51 ` Peter Stephenson
2000-10-31 14:01 ` Sven Wischnowsky
2000-10-31 15:25 ` Bart Schaefer
2000-10-31 15:43 ` Andrej Borsenkow
2000-10-30 10:25 Sven Wischnowsky
2000-10-30 8:32 Sven Wischnowsky
2000-10-30 9:56 ` Peter Stephenson
2000-10-30 10:10 ` Thomas Köhler
2000-10-30 16:18 ` Bart Schaefer
2000-10-24 7:53 Sven Wischnowsky
2000-10-21 12:34 Thomas Köhler
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=20001023171214.B15065@picard.franken.de \
--to=jean-luc@picard.franken.de \
--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).