From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers mailing list <zsh-workers@zsh.org>
Subject: Re: segfault on menu-select
Date: Sun, 15 Aug 2010 13:43:26 -0700 [thread overview]
Message-ID: <100815134326.ZM20936@torch.brasslantern.com> (raw)
In-Reply-To: <20100813214357.012f7f35@pws-pc>
On Aug 13, 9:43pm, Peter Stephenson wrote:
}
} I won't tell you what valgrind said, it was really quite rude. That and
} the core dumps I got seemed to point the finger at amatches.
Yes ... but I think it's indirect, something stored in *amatches rather
than amatches itself.
} It's not this simple, is it? It's a little difficult to see how this
} could be wrong, but this is the completion system we're talking about.
I agree there doesn't appear to be anything wrong with that patch, but it
also doesn't quite fix things. I no longer get a reproducible core dump,
but now menu-select is a silent no-op. (The minimal zshrc used so far is
still necessary to reproduce anything, as soon as I use my full startup I
get normal menu selection.)
next prev parent reply other threads:[~2010-08-15 20:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 14:46 Philipp Hartwig
2010-08-12 14:53 ` Frank Terbeck
2010-08-12 15:20 ` Philipp Hartwig
2010-08-12 15:49 ` Frank Terbeck
2010-08-12 16:53 ` Philipp Hartwig
2010-08-12 17:07 ` Frank Terbeck
2010-08-12 17:33 ` Philipp Hartwig
2010-08-12 18:04 ` Frank Terbeck
2010-08-12 23:07 ` Bart Schaefer
2010-08-13 8:08 ` Philipp Hartwig
2010-08-13 15:57 ` Bart Schaefer
2010-08-13 20:43 ` Peter Stephenson
2010-08-15 20:43 ` Bart Schaefer [this message]
2010-08-15 22:34 ` Bart Schaefer
2010-08-31 14:33 ` Philipp Hartwig
2010-09-06 4:11 ` Bart Schaefer
2011-01-09 18:56 ` Philipp Hartwig
2011-01-09 19:54 ` Bart Schaefer
2011-01-09 20:57 ` Philipp Hartwig
2010-08-12 16:04 ` Bart Schaefer
2010-08-12 17:03 ` Philipp Hartwig
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=100815134326.ZM20936@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).