From: Mikael Magnusson <mikachu@gmail.com>
To: Oliver Kiddle <okiddle@yahoo.co.uk>
Cc: Kamil Dudka <kdudka@redhat.com>, zsh-workers@zsh.org
Subject: Re: [PATCH] {,un}applychange: do not call zle_setline(NULL) if quietgethist() fails
Date: Fri, 28 Jun 2019 02:20:02 +0200 [thread overview]
Message-ID: <CAHYJk3Spwu6VvJmUc0+hxiFUUfBdB9rTXrdjv_qcwTnNgSvDLA@mail.gmail.com> (raw)
In-Reply-To: <797-1561676485.902916@C-Cf.WCnE.5Cn6>
I can reproduce *a* crash, not necessarily *the* crash, by making a
2x2 window and then maximizing/unmaximizing the window. It seems to
not reproduce if I have run any commands in the shell.
On 6/28/19, Oliver Kiddle <okiddle@yahoo.co.uk> wrote:
> Kamil Dudka wrote:
>> There is a bug report in Red Hat Bugzilla about zsh crashing on NULL
>> pointer dereference: https://bugzilla.redhat.com/1722703
>>
>> I was not able to reproduce the crash myself but the attached patch
>> should prevent zsh from crashing in this situation.
>
> It'd perhaps be good to add a DPUTS call here because while it is good
> not to crash the condition does perhaps indicate a bug and it'd be
> better not to hide it completely. I can't reproduce the crash either but
> there must be some plugins or url quoting magic going on here.
> More details of the setup used by the user might help find the
> underlying problem.
>
> Oliver
>
--
Mikael Magnusson
next prev parent reply other threads:[~2019-06-28 0:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 10:19 Kamil Dudka
[not found] ` <249696510.1723352.1561545091592@mail2.virginmedia.com>
2019-06-26 11:00 ` Fwd: " Peter Stephenson
2019-06-26 12:07 ` Kamil Dudka
2019-06-27 23:01 ` Oliver Kiddle
2019-06-28 0:20 ` Mikael Magnusson [this message]
2019-06-28 8:12 ` Kamil Dudka
2019-07-23 13:45 ` [PATCH v2] " Kamil Dudka
2019-07-26 15:24 ` Kamil Dudka
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=CAHYJk3Spwu6VvJmUc0+hxiFUUfBdB9rTXrdjv_qcwTnNgSvDLA@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=kdudka@redhat.com \
--cc=okiddle@yahoo.co.uk \
--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).