Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Re : Re: Re : [BUG] Crash due to malloc call in signal handler
- X-seq: zsh-workers 45082
- From: Peter Stephenson <p.stephenson@xxxxxxxxxxx>
- To: <zsh-workers@xxxxxxx>, Antoine C. <acalando@xxxxxxx>
- Subject: Re: Re : Re: Re : [BUG] Crash due to malloc call in signal handler
- Date: Wed, 18 Dec 2019 10:01:38 +0000
- Cms-type: 201P
- Dkim-filter: OpenDKIM Filter v2.11.0 mailout2.w1.samsung.com 20191218100139euoutp0204b96092ddae8a3342630166f96030a9~hburYfbR22776827768euoutp029
- In-reply-to: <1548982683.1013827769.1576607530234.JavaMail.root@zimbra62-e11.priv.proxad.net>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- List-unsubscribe: <mailto:zsh-workers-unsubscribe@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <CGME20191217183216epcas1p1e81fb3dc675bab810e8d29ac0f53242c@epcas1p1.samsung.com> <1548982683.1013827769.1576607530234.JavaMail.root@zimbra62-e11.priv.proxad.net>
On Tue, 2019-12-17 at 19:32 +0100, Antoine C. wrote:
> Good news(!), I finally get another crash with a backtrace, despite
> Peter's last patch. This one, like the previous, is triggered by debug
> code because of two simultaneous free() calls from main and signal
> contexts.
Great, thanks.
OK, the suspect here is the arithmetic code --- it looks like it's
running unprotected against signals, despite the fact it can set
variables. Arithmetic is a quick operation, so hopefully we can block
fairly high up the stack. I should get a chance to look later
(but I don't think this is rocket science from this point on so maybe
someone will beat me to it).
pws
> #9 0x000055e115ce40f4 in zhandler (sig=17) at signals.c:648
...
> #23 0x000055e115c7cddf in execarith (state=0x7ffea5b39110, do_exec=0) at exec.c:5111
Messages sorted by:
Reverse Date,
Date,
Thread,
Author