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: Fri, 30 Sep 2016 23:54:52 +0200 [thread overview]
Message-ID: <CAKc7PVA1nmYEgCRDunMWjHUEEhhO7QdR4PX3kThB=x-4Kq0U6g@mail.gmail.com> (raw)
In-Reply-To: <160930144528.ZM17296@torch.brasslantern.com>
On 30 September 2016 at 23:45, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Sep 30, 1:28pm, Sebastian Gniazdowski wrote:
> }
> } The stack trace is at the end.
>
> Is this a trace from a place where you sometimes get a core dump or
> unexpected exit? Because I don't see indication in the stack trace
> that menu selection is active, for example.
No, no luck with the crashes. It's a stack trace after Ctrl-C when in
.recursiveedit, i.e. when the Ctrl-R widget was invoked. The stressors
were commented out in zshrc. BTW. I was running multiple jobs because
on IRC one user said that he gets crashes when multiple jobs in
background. Didn't ask of ZSH_VERSION. Tomorrow will try with Zconvey
disabled, the Ctrl-C problems appeared after additional complex-char
mappings (e.g. cursors) so there should be something to examine.
Best regards,
Sebastian Gniazdowski
prev parent reply other threads:[~2016-10-01 0:48 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
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 [this message]
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='CAKc7PVA1nmYEgCRDunMWjHUEEhhO7QdR4PX3kThB=x-4Kq0U6g@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).