* completion.so segfaulting - debugging options?
@ 2009-02-13 0:07 kba
2009-02-13 3:52 ` Andrey Borzenkov
0 siblings, 1 reply; 3+ messages in thread
From: kba @ 2009-02-13 0:07 UTC (permalink / raw)
To: zsh-users
hi zsh users,
I have recently been playing a lot with zsh's completion, adding
snippets from different sources and trying a lot of things. Now I do
have a very sophisticated (read: cluttered) completion setup, thank you
very much :-) Amazing software, really.
The problem is that somewhere in all the setopts and zstyles I have
introduced a bug that leads to zsh segfaulting during completion in
certain conditions I can't reproduce properly. I try to complete a path,
the colorized list of possibilities pops up, I press another key and zsh
quits and in /var/log/messages.log a line
> [13365.361881] zsh[20379]: segfault at 0000000c eip b7c83d1d esp bfde47f0 error 6
pops up. But not always and seemingly not always under the (seemingly)
same conditions.
Now I know, that this is no good bug reporting, so I wanted to know if
there are any options/settings I might try to narrow the problem down
myself and find the cause for it. Can the completion process be
traced/logged, a la "at this point we switch to list-mode, at this point
we switch to menu completion, at this point we segfault"?
Thanks a lot for any hint
kba
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: completion.so segfaulting - debugging options?
2009-02-13 0:07 completion.so segfaulting - debugging options? kba
@ 2009-02-13 3:52 ` Andrey Borzenkov
2009-02-18 14:19 ` kba
0 siblings, 1 reply; 3+ messages in thread
From: Andrey Borzenkov @ 2009-02-13 3:52 UTC (permalink / raw)
To: zsh-users; +Cc: kba
[-- Attachment #1: Type: text/plain, Size: 691 bytes --]
On 13 of February 2009 03:07:26 kba wrote:
[...]
> The problem is that somewhere in all the setopts and zstyles I have
> introduced a bug that leads to zsh segfaulting during completion in
> certain conditions I can't reproduce properly.
[...]
>
> Now I know, that this is no good bug reporting, so I wanted to know
> if there are any options/settings I might try to narrow the problem
> down myself and find the cause for it.
Your best bet is to find a reliable way to reproduce it and post to zsh-
workers. Also try using current CVS version, there were same crash
fixes. But again, unless you can reproduce this bug at will, you never
know whether this is fixed or not.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: completion.so segfaulting - debugging options?
2009-02-13 3:52 ` Andrey Borzenkov
@ 2009-02-18 14:19 ` kba
0 siblings, 0 replies; 3+ messages in thread
From: kba @ 2009-02-18 14:19 UTC (permalink / raw)
To: zsh-users
On Fri, Feb 13, 2009 at 06:52:39AM +0300, Andrey Borzenkov wrote:
> Your best bet is to find a reliable way to reproduce it and post to zsh-
> workers. Also try using current CVS version, there were same crash
> fixes. But again, unless you can reproduce this bug at will, you never
> know whether this is fixed or not.
Just in case someone has the same problem and stumbles over this post:
I just read this thread [1] about zsh crashing when 'interactive' is set
as a menu-completion option. That was my problem too, apparently. I just
compiled zsh from CVS as you proposed and so far and the crash didn't
happen again (yet :D)
[1] http://bbs.archlinux.org/viewtopic.php?id=35706
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-02-18 14:20 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-02-13 0:07 completion.so segfaulting - debugging options? kba
2009-02-13 3:52 ` Andrey Borzenkov
2009-02-18 14:19 ` kba
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).