Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Where to start debugging zle recursive-edit? / Ctrl-C
- X-seq: zsh-workers 39494
- From: Sebastian Gniazdowski <sgniazdowski@xxxxxxxxx>
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- Subject: Re: Where to start debugging zle recursive-edit? / Ctrl-C
- Date: Thu, 29 Sep 2016 11:30:20 +0200
- Cc: Zsh hackers list <zsh-workers@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=9o8BVVHSTtUa2y4U+D/ZquLMQ1zDmVBhFybY8JDSdY8=; b=jB8rh2vST/l/D/IaxUmAcXQ08XQarcX2S0w4TGMwuWyyuY3mSaFxLI492iHf2eiSlM bkqZqNTngd0BAJ3/9u3C8TCWclSJnJ448Shdg+b5wulMl56/oc5rBUJCsGqUiK8+upN/ jPCJ0Z36IWHvFKDTWyj0GGlnAVoBO3KSO6Xr1qWMifsUQGjqREHfuUnBAXZXBgPjsiXw TpsO0TSCY9sOUgMA3gFA0ZqBNjhWyRJH12QatG2nedZxzsfwzw7VoDye0Xy2M0cKkciJ t8vPSexnRyNsRVXxurzNqCC/1ynpnf1kEyf8M/LaLcbTjgmooS8YdYkvtcxGOH8wbWvD vnqw==
- In-reply-to: <160927090957.ZM12910@torch.brasslantern.com>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <CAKc7PVBvm+u5QQQZo+6QEQw4bRHx1br5K-A6y_6pAuP8+KCbcQ@mail.gmail.com> <160924133140.ZM29034@torch.brasslantern.com> <CAKc7PVDu6pPaPWHSOp4dOU8+yXE_12OVccyCcXh=_=DqWVRRaw@mail.gmail.com> <160927090957.ZM12910@torch.brasslantern.com>
On 27 September 2016 at 18:09, Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
> On Sep 27, 12:16am, Sebastian Gniazdowski wrote:
> }
> } have unoptimized HEAD Zsh, coredumps are set up, added some stressing
>
> If you're not seeing the problem under these circumstances, then it's
> probably a race condition that's eliminated either by taking out the
> code optimization or by adding the other processing.
It seems so, hours after I switched to CFLAGS=-O2 compiled binary,
I've got a suspicious effect, after smoothly running no-opt binary for
few days – couldn't recall if I spotted anything suspicious. The
effect is message at shell startup:
TRAPALRM: scalar parameter abcdef created globally in function TRAPALRM"
It appeared just once, not long after switching to -O2. I don't use
warn_create_global, and did a test that Mikael suggested to ensure:
function setopt() { print -r - "$funcfiletrace[1]: $0 ${(q-)@}" >>!
/tmp/setopt_data; builtin $0 "$@" }
and only "setopt localoptions warncreateglobal" from z-sy-h was
reported. Zshrc has at the end:
TRAPALRM() { abcdef=$(( abcdef + 1 )); }
TMOUT=1
PERIODIC_HOOK() { efghij=$(( efghij + 1 )); }
PERIOD=1
add-zsh-hook periodic PERIODIC_HOOK
repeat 50; do sleep 1000000 &; done
coproc cat
My aim is .recursive-edit and Ctrl-C, but just want to hook at
something first, have any backtrace, I suspect it will be easy to
connect with problems with .recursive-edit even when not directly
related to it. Crash related to Ctrl-C appeared in uncanny situations
AFAIR like Ctrl-R, Ctrl-C multiple times, then menu search completion
with also Ctrl-C, something like this, hard to reproduce.
Best regards,
Sebastian Gniazdowski
Messages sorted by:
Reverse Date,
Date,
Thread,
Author