zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: Re : [BUG] Crash due to malloc call in signal handler
Date: Mon, 16 Dec 2019 17:08:23 +0000	[thread overview]
Message-ID: <1576516103.4950.14.camel@samsung.com> (raw)
In-Reply-To: <896178036.1008341150.1576515852191.JavaMail.root@zimbra62-e11.priv.proxad.net>

On Mon, 2019-12-16 at 18:04 +0100, Antoine C. wrote:
> I have tried this patch: https://protect2.fireeye.com/url?k=1b67e963-46f97289-1b66622c-0cc47a6cba04-bb264a20abb211dd&u=https://www.zsh.org/mla/workers/2019/msg01058.html
> 
> The good news (actually a bad one as I will explain) is that I could not 
> reproduce it with my specific test script. With the original code, 
> it usually occurs within seconds; with the patch, I never get a crash 
> even after hours of execution, and trying to modify some delays.
> 
> But I also tried with my "real life" scripts, and unfortunately I get a
> crash  twice today. There is a difference with previous version: the crash 
> usually occurred within minutes or a few hours, and now it is rather after 
> many hours.

Does sound like progress, thanks for the update.

> Here is a bt:

As you suspected, that's a normal, unsuspicious execution, with no signals
involved, so indeed it's probably already in a bad state.

pws

      reply	other threads:[~2019-12-16 17:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20191216170510eucas1p283887e166264bb37b583793784a89d56@eucas1p2.samsung.com>
2019-12-16 17:04 ` Antoine C.
2019-12-16 17:08   ` Peter Stephenson [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=1576516103.4950.14.camel@samsung.com \
    --to=p.stephenson@samsung.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).