Zsh Mailing List Archive
Messages sorted by:
Re: Bug - invalid pointer
- X-seq: zsh-workers 42635
- From: John Ramsden <ramsdenj@xxxxxxxxxx>
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- Subject: Re: Bug - invalid pointer
- Date: Fri, 13 Apr 2018 18:43:24 -0700
- Cc: zsh-workers@xxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1523670206; bh=QxPAylxwHtOfszxNNPXvz+J1g4XRhY0U7zw/fItZygQ=; h=From:To:Cc:Date:In-Reply-To:References:Subject:From; b=RGkldjFeBscIXseO1z+aJxu01EUIrjorhm0yw1JZfPCTMMPUJXOW4VwZrmrMz8nn2 ZFCiodYmVdxO4uBM/zNEEmCGJUl+hMwVmrz13ko8YZ7cmjcwXMvuNqh2EK8Q1COnUv wS9NWVfYA7u84NGnw5CiExuHUfBdDOKYEI/6em0o=
- In-reply-to: <email@example.com>
- List-help: <mailto:firstname.lastname@example.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:email@example.com>
- List-unsubscribe: <mailto:firstname.lastname@example.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <1523656615.2631939.1337422824.550CF732@webmail.messagingengine.com> <email@example.com> <CAH+w=7ZXrGFgcZW_CkBdZ+tWjwQGxK0jmyN3G3xWB6=jmom3Tw@mail.gmail.com>
Should I recompile with debugging symbols and let you know what shows up? How would you like me to proceed to help debug the issue?
On Fri, Apr 13, 2018, at 6:29 PM, Bart Schaefer wrote:
> 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: