Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
[BUG?] Very strange behavior, execution of a function is interrupted
- X-seq: zsh-workers 43360
- From: Sebastian Gniazdowski <sgniazdowski@xxxxxxxxx>
- To: Zsh hackers list <zsh-workers@xxxxxxx>
- Subject: [BUG?] Very strange behavior, execution of a function is interrupted
- Date: Sat, 1 Sep 2018 00:01:58 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=gbC8PR2veYppwU6zQc2w9FijpNRN3u6LI55E2BHXQPQ=; b=pOOuRAt0jkhE7ouKPeQkgDJ4A/2zd/pF8xp7sl+4WUso/GE/9rWusv91C5e7MrV3ZL bCjHdt1MOxVlZG4b6kONxHDZuK/32G+36gLmk0JMw1h2cERuEdLxtl43cVDnv5VX9/I1 zKxBpZuDtJdc6ABWbhTF4Suf71jYFhg2v8zd6aycCUrsE59F6SKNw5cWTQsOjAEhiTEq gWAqT702JvemXePLK0AIfBnoKaG7tyqyLMmv9tE5jDDwThyJc82R0vrg9XyCfEUU45Da j1tU3dTqVIu/LaOQe18yy2nX6P8hQk3Ln3YS3w9YdGKfmRJSXIVhGiK/C+BXUPs9AORp ehqQ==
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- List-unsubscribe: <mailto:zsh-workers-unsubscribe@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
Hello,
it's quite a lost game to explain this, but I'll try:
- there is a scheduler called from sched +1 and once from zle -F
- it detects timed-out tasks, moves them to ZPLG_RUN, then executes
them reading them from this array
Problem: sometimes execution never reaches this line and beyond:
https://github.com/zdharma/zplugin/blob/7a24478e5862a1359b6cfb2887a792213be07e3a/zplugin.zsh#L1485
Some cycles of the preceding loop are then also skipped.
I feel very helpless in explaining this, maybe there's standard
questions sheet for situation where bug in exec.c is suspected?
I know `break 2' inside a function will break out of loop that
contains the function call. But I don't know what could exit a
function. I have debug prints and observe this clearly. At the
mentioned line, no execution occurs, ZPLG_RUN isn't cleared, I get to
run some tasks twice.
Twice when I checked, it was happening when zle -F was called so near
next second, that timeout'd tasks detection included two time slots:
"0" (0 seconds after first precmd, handled by zle -F) and "1" (1
second after first precmd, handled by sched +1).
--
Sebastian Gniazdowski
News: https://twitter.com/ZdharmaI
IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin
Blog: http://zdharma.org
Messages sorted by:
Reverse Date,
Date,
Thread,
Author