From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Segfault on "task <Tab><Tab>" with zsh 5.0.2 (minimal dataset to reproduce the issue found)
Date: Tue, 17 Sep 2013 20:05:51 -0700 [thread overview]
Message-ID: <130917200551.ZM14080@torch.brasslantern.com> (raw)
In-Reply-To: <20130917200546.6094eb98@pws-pc.ntlworld.com>
On Sep 17, 8:05pm, Peter Stephenson wrote:
}
} Well, completion's very slow, suggesting something fairly heavy is
} happening, but it hasn't crashed yet. I don't suppose it's memory
} exhaustion? The shell's not very robust about that.
The stack trace from the very first message in the thread indicates
it dies dereferencing the descr field of a Cvdef structure from the
cvdef_cache array. The trace doesn't show the call to zsfree so it
is the Cvdef pointer itself that is bad, not the struct contents.
The valgrind output confirms this, which seems to indicate that the
cvdef_cache array is being scribbled on ... but that's static memory,
so it would have to be from overflowing some adjacent static storage
(?) and 0x100000001 looks suspicious as a value that's repeatably so
scribbled.
A watchpoint on cvdef_cache[0] might shed some light.
next prev parent reply other threads:[~2013-09-18 3:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 22:18 Segfault on "task <Tab><Tab>" with zsh 5.0.2 Axel Beckert
2013-09-13 8:37 ` Peter Stephenson
2013-09-13 11:34 ` Axel Beckert
2013-09-13 11:51 ` Peter Stephenson
2013-09-13 12:24 ` Axel Beckert
2013-09-13 12:36 ` Peter Stephenson
2013-09-13 19:33 ` Pierre Schmitz
2013-09-16 16:17 ` Ivan S. Freitas
2013-09-16 17:18 ` Axel Beckert
2013-09-17 8:56 ` Peter Stephenson
2013-09-17 16:10 ` Segfault on "task <Tab><Tab>" with zsh 5.0.2 (minimal dataset to reproduce the issue found) Axel Beckert
2013-09-17 16:35 ` Axel Beckert
2013-09-17 19:05 ` Peter Stephenson
2013-09-17 20:12 ` Axel Beckert
2013-09-18 3:05 ` Bart Schaefer [this message]
2013-09-18 21:50 ` Segfault on "task <Tab><Tab>" with zsh 5.0.2 [PATCH] Axel Beckert
2013-09-19 8:49 ` Peter Stephenson
2013-09-19 14:42 ` Bart Schaefer
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=130917200551.ZM14080@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
/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).