zsh-workers
 help / color / mirror / code / Atom feed
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Where to start debugging zle recursive-edit? / Ctrl-C
Date: Tue, 27 Sep 2016 00:16:13 +0200	[thread overview]
Message-ID: <CAKc7PVDu6pPaPWHSOp4dOU8+yXE_12OVccyCcXh=_=DqWVRRaw@mail.gmail.com> (raw)
In-Reply-To: <160924133140.ZM29034@torch.brasslantern.com>

Hello,
have unoptimized HEAD Zsh, coredumps are set up, added some stressing
things to zshrc: TMOUT=1 function, PERIOD=1 hook, repeat 50; do sleep
1000000 &; done, coproc cat – and I'm waiting. The issue wasn't very
active in past two days and there was no good reason to start lldb.
PS. Any ideas of how to stress Zsh more?

Best regards,
Sebastian Gniazdowski


  parent reply	other threads:[~2016-09-26 22:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-23 16:26 Sebastian Gniazdowski
2016-09-24 20:31 ` Bart Schaefer
2016-09-24 20:58   ` Sebastian Gniazdowski
2016-09-25  7:09     ` Daniel Shahaf
2016-09-26 22:16   ` Sebastian Gniazdowski [this message]
2016-09-27 16:09     ` Bart Schaefer
2016-09-29  9:30       ` Sebastian Gniazdowski
2016-09-29 17:07         ` Bart Schaefer
2016-09-30  9:04   ` Sebastian Gniazdowski
2016-09-30 11:28   ` Sebastian Gniazdowski
2016-09-30 13:30     ` Sebastian Gniazdowski
2016-09-30 20:44       ` Bart Schaefer
2016-10-02 16:26         ` Sebastian Gniazdowski
2016-10-02 17:37           ` Sebastian Gniazdowski
2016-10-05  5:31         ` Sebastian Gniazdowski
2016-10-05  6:14           ` Bart Schaefer
2016-10-05 10:27             ` Sebastian Gniazdowski
2016-10-05 18:31               ` Bart Schaefer
2016-10-05 20:36                 ` Sebastian Gniazdowski
2016-09-30 21:45     ` Bart Schaefer
2016-09-30 21:54       ` Sebastian Gniazdowski

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='CAKc7PVDu6pPaPWHSOp4dOU8+yXE_12OVccyCcXh=_=DqWVRRaw@mail.gmail.com' \
    --to=sgniazdowski@gmail.com \
    --cc=schaefer@brasslantern.com \
    --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).