From: Clint Adams <schizo@debian.org>
To: zsh-workers@sunsite.dk
Cc: "Frode E. Moe" <frode@coretrek.com>,
Debian Bug Tracking System <314597-forwarded@bugs.debian.org>
Subject: Re: Bug#314597: zsh segfaults randomly when tabcompleting file with lots of spaces
Date: Fri, 17 Jun 2005 14:28:49 -0400 [thread overview]
Message-ID: <20050617182849.GA1759@scowler.net> (raw)
In-Reply-To: <20050617110002.C4AF22B47A@nexus.intra.coretrek.com>
I have not yet been able to reproduce this.
> Hi, while dealing with a virus attachment to an email I received, zsh
> segfaulted while tabcompleting the file name.
>
> The file name is:
> instructions.htm .scr
>
> (i.e. "instructions.htm" + a lot of spaces + ".scr", obviously an
> attempt to trick windows users into running an executable).
>
> I haven't found a way to reproduce this every time, but the following
> seems to trigger a segfault after a few iterations:
>
> touch instructions.htm\ \ \ \ \ \ ........lots of spaces ....\ \.scr<enter>
> mkdir k<enter>
> mv ins<tab> k <ctrl+c>
> mv ins<tab> k <ctrl+c>
> strings ins<tab>
>
> Here's a gdb 'bt' backtrace from when the bug occurs:
>
> (gdb) bt
> #0 0xb7e9c33b in strlen () from /lib/tls/libc.so.6
> #1 0xb7c4837d in unambig_data () from
> /usr/lib/zsh/4.2.5/zsh/complete.so
> #2 0xb7c48e76 in do_single () from /usr/lib/zsh/4.2.5/zsh/complete.so
> #3 0xb7c4989c in do_menucmp () from /usr/lib/zsh/4.2.5/zsh/complete.so
> #4 0xb7beb702 in ?? () from /usr/lib/zsh/4.2.5/zsh/complist.so
> #5 0x00000000 in ?? ()
> #6 0x00000000 in ?? ()
> #7 0x0000000a in ?? ()
> #8 0x00000000 in ?? ()
> #9 0xb7e95dcb in free () from /lib/tls/libc.so.6
> #10 0x0808833a in runhookdef ()
> #11 0xb7c3b020 in after_complete () from
> /usr/lib/zsh/4.2.5/zsh/complete.so
> #12 0x0808837e in runhookdef ()
> #13 0xb7c6ce02 in parambeg () from /usr/lib/zsh/4.2.5/zsh/zle.so
> #14 0xb7c6c27b in expandorcomplete () from /usr/lib/zsh/4.2.5/zsh/zle.so
> #15 0xb7c6bebd in completecall () from /usr/lib/zsh/4.2.5/zsh/zle.so
> #16 0xb7c61587 in execzlefunc () from /usr/lib/zsh/4.2.5/zsh/zle.so
> #17 0xb7c60c37 in zlecore () from /usr/lib/zsh/4.2.5/zsh/zle.so
> #18 0xb7c611df in zleread () from /usr/lib/zsh/4.2.5/zsh/zle.so
> #19 0x08077ea2 in ingetc ()
> #20 0x08077c61 in ingetc ()
> #21 0x080701ce in iaddtoline ()
> #22 0x0807d776 in gettok ()
> ---Type <return> to continue, or q <return> to quit---
> #23 0x0807d165 in yylex ()
> #24 0x08090f27 in parse_event ()
> #25 0x0807500a in loop ()
> #26 0x08077962 in zsh_main ()
> #27 0x0805268b in main ()
>
> Here's some of the .zshrc options I use:
>
> setopt menucomplete
> setopt autolist
> autoload -U compinit
> compinit
> zmodload -i zsh/complist
> zstyle ':completion:*' menu select=0
> zstyle ':completion:*:default' list-colors ${(s.:.)LS_COLORS}
>
parent reply other threads:[~2005-06-17 18:29 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20050617110002.C4AF22B47A@nexus.intra.coretrek.com>]
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=20050617182849.GA1759@scowler.net \
--to=schizo@debian.org \
--cc=314597-forwarded@bugs.debian.org \
--cc=frode@coretrek.com \
--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).