From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Methods of shadowing a builtin call
Date: Fri, 29 Jan 2016 22:33:39 +0100 [thread overview]
Message-ID: <CAKc7PVAS=iT0t6exL8Z+xYrnyN1O7zx_MEu0smnWXRyq8X6VrA@mail.gmail.com> (raw)
Hello,
I shadow setopt to gather data of what is being done in sourced
script. I currently use alias setopt=--setopt-shadow and then source a
script. This works fine except for z-sy-h. For that project, when I
source it with the alias being in place, interiors of it then still
use the shadowing function during their later operations. How to
suppress this? Self-insert is in some way catched by z-sy-h, and each
keypress invokes my shadowing function.
When I change:
alias setopt=--shadow-setopt
to:
setopt() { --shadow-setopt "$@" }
then Zsh segfaults. I'm not sure if on OS X gdb gives meaningful
output, but this is the backtrace:
Program received signal SIGSEGV, Segmentation fault.
0x00000001000184e4 in execrestore ()
(gdb) bt
#0 0x00000001000184e4 in execrestore ()
#1 0x00000001000135c4 in execlist ()
#2 0x0000000100012c27 in execlist ()
#3 0x0000000100012818 in execode ()
#4 0x0000000100016be2 in runshfunc ()
#5 0x0000000100016540 in doshfunc ()
#6 0x0000000100017ca6 in execrestore ()
#7 0x000000010001c031 in execrestore ()
#8 0x00000001000135c4 in execlist ()
#9 0x0000000100012d84 in execlist ()
#10 0x000000010003efae in execif ()
...
How to explain the segfault?
Is there any third method of attaching to setopt?
Best regards,
Sebastian Gniazdowski
next reply other threads:[~2016-01-29 21:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 21:33 Sebastian Gniazdowski [this message]
2016-01-29 22:20 ` Sebastian Gniazdowski
2016-01-29 23:09 ` Bart Schaefer
2016-01-30 9:31 ` Sebastian Gniazdowski
2016-01-30 20:48 ` 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='CAKc7PVAS=iT0t6exL8Z+xYrnyN1O7zx_MEu0smnWXRyq8X6VrA@mail.gmail.com' \
--to=sgniazdowski@gmail.com \
--cc=zsh-users@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).