Zsh Mailing List Archive
Messages sorted by:
Re: Bug - invalid pointer
- X-seq: zsh-workers 42634
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: John Ramsden <ramsdenj@xxxxxxxxxx>
- Subject: Re: Bug - invalid pointer
- Date: Fri, 13 Apr 2018 18:29:32 -0700
- Cc: "zsh-workers@xxxxxxx" <zsh-workers@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ULhFt/BSMueKRVIrsJblsiTTatfLiSnZBu5EFtdsKWA=; b=H1iG/JoNLf+VvQ5xKeo5ksxpkmQDOH/noaM4nW6JXdFprPBs+Mta8+uVjV5Jx1kFsF GmMsqMRUtfXyx1evOyXQHRHdu00RqPJ1+xyWyQfde4tD2fcJJNTzauNO2XNlBgeeydOy n2G3gzg0tGYcwFH8yxDI62T3tGd9Y55moV7nztBoK9SKaHAzpejYiJUnaNYoCvSA4E25 JLRbehSK/fLm8YF0EINq6QpYHdW0yH9EWLtluzk+aUl0zMjbsEig2s7sjeQg181Lefb/ tK4aJbxQBgda/PIBf0rnLw0n/pke5jvsA4cenYVph8Ll4UKlpApF63j/t3+1t144QVj/ gNxA==
- In-reply-to: <1523656615.2631939.1337422824.550CF732@webmail.messagingengine.com>
- List-help: <mailto:email@example.com>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:firstname.lastname@example.org>
- List-unsubscribe: <mailto:email@example.com>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <1523656615.2631939.1337422824.550CF732@webmail.messagingengine.com>
On Fri, Apr 13, 2018 at 2:56 PM, John Ramsden <ramsdenj@xxxxxxxxxx> 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.
Messages sorted by: