From: Thorsten Kampe <thorsten@thorstenkampe.de>
To: zsh-users@sunsite.dk
Cc: zsh-workers@sunsite.dk
Subject: Re: zsh 4.2.0 dumping core on completion attempt
Date: Wed, 26 May 2004 00:53:17 +0200 [thread overview]
Message-ID: <1kfucegia4ux3.dlg@thorstenkampe.de> (raw)
In-Reply-To: <20040525063239.19784.qmail@web51107.mail.yahoo.com>
* Felix Rosencrantz (2004-05-25 08:32 +0100)
> One thing that would help others to reproduce your problem is to provide a
> minimal "zsh -f" cut&paste script that reproduces the problem. It would even
> be better if you can include a stack trace from your core dumps, or a valgrind
> report.
I have no idea how to use "valgrind".
> All these will make it much easier for the folks who might fix the
> bug to find the problem.
>
> Here is a possible start of such a script:
> zsh -f
> autoload -U compinit; compinit -C
> zstyle ':completion:*' matcher-list 'm:[-._]=[-._] r:|[-./_]=**'
> mkdir bug ; cd bug
>
> ls _f<TAB>
> <CORE DUMP>
>
> Note that matching specs depend on the possible completion matches. So try to
> find a minimal set of files to touch, that cause the core dump you see. I
> tried your spec, and didn't get a core dump.
zsh -f
autoload -U compinit; compinit -C
zstyle ':completion:*' matcher-list 'm:[-._]=[-._] r:|[-./_]=**'
mkdir bug; cd bug
_f<TAB>
zsh: 2588 segmentation fault zsh -f
The linux zsh produces no coredump but fortunately the Cygwin does
(although I have disabled it via "ulimit -Sc 0")
% cat zsh.exe.stackdump
Exception: STATUS_ACCESS_VIOLATION at eip=610D3BE2
eax=0000005F ebx=00000000 ecx=00000000 edx=0A1016C3 esi=0A1016C3
edi=00000000
ebp=0022A308 esp=0022A2F4 program=C:\cygwin\bin\zsh.exe, pid 2588,
thread main
cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
Stack trace:
Frame Function Args
0022A308 610D3BE2 (0A1016C3, 00000000, 00000001, 00000001)
0022A328 66F4DFFD (0A0FC558, 0A0EC960, 00000001, 0A101748)
0022A368 66F4F16B (0A0EC960, 0A0FC558, 0A1016C4, 00000003)
0022A468 66F495EF (00000000, 0A1016E0, 0A0E0BD0, 0A0FC558)
0022A5A8 66F485ED (0022A5D0, 0A0D6270, 00000000, 00000000)
0022A648 66F41EE6 (0A082578, 0022A660, 0022A6C0, 00000000)
0022A768 66FE1A7F (0A0824E8, 66F56300, 00000001, 0022A81C)
0022A898 66FF2CB5 (0022B590, 00000000, 00000000, 00000012)
0022A8E8 66FF131D (0022B590, 00001183, 00000012, 00000000)
0022A948 66FF0A83 (0022B590, 00001802, 00000012, 00000000)
0022A988 66FF07F1 (0022B590, 00000001, 00000000, 66FF46DF)
0022A9B8 6700F411 (0022B590, 00000000, 00000001, 0022AA6C)
0022AAE8 66FF2A85 (0022B590, 00000000, 00000000, 00000012)
0022AB38 66FF131D (0022B590, 00001143, 00000012, 00000000)
0022AB98 66FF0A83 (0022B590, 00004802, 00000012, 00000000)
0022ABD8 66FF07F1 (0022B590, 00000001, 00000000, 66FF46DF)
End of stack trace (more stack frames may be present)
Thorsten
next prev parent reply other threads:[~2004-05-25 22:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-22 13:54 Thorsten Kampe
2004-05-25 6:32 ` Felix Rosencrantz
2004-05-25 22:53 ` Thorsten Kampe [this message]
2004-05-28 5:40 ` Felix Rosencrantz
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=1kfucegia4ux3.dlg@thorstenkampe.de \
--to=thorsten@thorstenkampe.de \
--cc=zsh-users@sunsite.dk \
--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).