zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: John Ramsden <ramsdenj@riseup.net>
Cc: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: Bug - invalid pointer
Date: Fri, 13 Apr 2018 18:29:32 -0700	[thread overview]
Message-ID: <CAH+w=7ZXrGFgcZW_CkBdZ+tWjwQGxK0jmyN3G3xWB6=jmom3Tw@mail.gmail.com> (raw)
In-Reply-To: <1523656615.2631939.1337422824.550CF732@webmail.messagingengine.com>

On Fri, Apr 13, 2018 at 2:56 PM, John Ramsden <ramsdenj@riseup.net> wrote:
>
> This only happens in dolphin, and only upon opening a new dolphin window. If I close and re-open the terminal panel, there is no crash.
>
> Downgrade of zsh (5.5-1 => 5.4.2-2) fixes the issue.
>
> 1 - https://bugs.kde.org/show_bug.cgi?id=393058

Took a quick look at that -- the stack traces aren't very useful
because zsh was not compiled with debugging symbols, so no line
numbers or source file names.  However, there have been literally no
changes to the code where you're encountering the error (zrefresh et
al) since 5.4.1, so there must be a bad allocation somewhere else that
is only manifesting when you reach that point.

In fact it's pretty likely to be some kind of signal-management thing
causing malloc re-entrance.


  reply	other threads:[~2018-04-14  1:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-13 21:56 John Ramsden
2018-04-14  1:29 ` Bart Schaefer [this message]
2018-04-14  1:43   ` John Ramsden
2018-04-14  1:57     ` Bart Schaefer
2018-04-14  2:00 John Ramsden
2018-04-14  2:16 ` Bart Schaefer
2018-04-14  3:19   ` John Ramsden
2018-04-14  3:57     ` Bart Schaefer
2018-04-14  5:34       ` John Ramsden
2018-04-14 10:20         ` Julien Nicoulaud
2018-04-14 19:34           ` Bart Schaefer

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='CAH+w=7ZXrGFgcZW_CkBdZ+tWjwQGxK0jmyN3G3xWB6=jmom3Tw@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=ramsdenj@riseup.net \
    --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).