From: Joel Bernstein <joel@fysh.org>
To: zsh-workers@zsh.org
Subject: segfault due to chpwd_function
Date: Fri, 11 Dec 2009 17:36:47 +0000 [thread overview]
Message-ID: <0742D8B8-F67E-48F7-BCCC-3F578A78D4B7@fysh.org> (raw)
I found a scenario leading to a segfault caused by a chpwd_function. The function in question runs to completion when called from command line directly after the 'cd' command, if it is removed from chpwd_functions and called manually. The chpwd_function in question calls the "prompt" function.
Curiously, if I add debug prints to my chpwd_function and precmd_function, I see that the chpwd_function completes and the precmd_function is not entered. Thus I conclude that some state is mutated by my chpwd_function (e.g. use of prompt()?) which causes zsh to segfault after running it.
The segfault (on e.g. cd ~/foo) looks like:
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000000000007075
0x0000000100020be4 in hasher ()
(gdb) bt
#0 0x0000000100020be4 in hasher ()
#1 0x0000000100020c2b in gethashnode ()
#2 0x0000000100069995 in callhookfunc ()
#3 0x000000010000f057 in bin_cd ()
#4 0x000000010000cf0b in execbuiltin ()
#5 0x0000000100016adb in execcmd ()
#6 0x0000000100017995 in execpline2 ()
#7 0x0000000100017d7c in execpline ()
#8 0x0000000100018e27 in execlist ()
#9 0x0000000100018f65 in execode ()
#10 0x000000010002ab27 in loop ()
#11 0x000000010002bf74 in zsh_main ()
#12 0x0000000100001374 in start ()
And my chpwd_function looks like:
prompt_chpwd () {
current_prompt=$(prompt -c | tail -n1 | perl -pe 's/\W//g')
zgit_isgit && {
if [ "$current_prompt" != "wunjo" ]
then
prompt wunjo
fi
} || {
if [ "$current_prompt" != "joel" ]
then
prompt joel
fi
}
}
I believe I can workaround this issue by setting the desired prompt theme to a var in my chpwd_function and calling prompt() from my precmd_function but it seems an odd behaviour and perhaps a bug?
I am running zsh 4.3.10 (i386-apple-darwin10.0.0).
Please let me know if I can provide more information.
/joel
next reply other threads:[~2009-12-11 17:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 17:36 Joel Bernstein [this message]
2009-12-11 17:52 ` Joel Bernstein
2009-12-11 18:11 ` Bart Schaefer
2009-12-11 18:41 ` Peter Stephenson
2009-12-11 19:01 ` Bart Schaefer
2009-12-11 22:16 ` Peter Stephenson
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=0742D8B8-F67E-48F7-BCCC-3F578A78D4B7@fysh.org \
--to=joel@fysh.org \
--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).