From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id 48d2c8a3 for ; Fri, 13 Dec 2019 09:40:51 +0000 (UTC) Received: (qmail 10448 invoked by alias); 13 Dec 2019 09:40:44 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: X-Seq: 45012 Received: (qmail 10140 invoked by uid 1010); 13 Dec 2019 09:40:44 -0000 X-Qmail-Scanner-Diagnostics: from mailout2.w1.samsung.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.1/25656. spamassassin: 3.4.2. Clear:RC:0(210.118.77.12):SA:0(-7.0/5.0):. Processed in 3.503024 secs); 13 Dec 2019 09:40:44 -0000 X-Envelope-From: p.stephenson@samsung.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _spf.samsung.com designates 210.118.77.12 as permitted sender) DKIM-Filter: OpenDKIM Filter v2.11.0 mailout2.w1.samsung.com 20191213094003euoutp02abe54dc720972e8cbcf46c86db85b3e0~f5NY1BWTe0284802848euoutp02B X-AuditID: cbfec7f2-f0bff7000001ef66-90-5df35c7209c3 Message-ID: <1576230001.5214.1.camel@samsung.com> Subject: Re: [BUG] Crash due to malloc call in signal handler From: Peter Stephenson To: Date: Fri, 13 Dec 2019 09:40:01 +0000 In-Reply-To: <2022943386.989309814.1576175339554.JavaMail.root@zimbra62-e11.priv.proxad.net> X-Mailer: Evolution 3.18.5.2-0ubuntu3.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPIsWRmVeSWpSXmKPExsWy7djPc7pFMZ9jDeaeUbc42PyQyYHRY9XB D0wBjFFcNimpOZllqUX6dglcGe8m72AueMFd8fWpWAPjDK4uRk4OCQETieW/Z7F3MXJxCAms YJT4/u4dG4TTxyQx6dMPqEwvk8SUIxNZYVq2r97NCpFYzigx8/odRriq6zd3QzlnGCW2T5gI 1X+BUeL+o5lg/bwChhJ/Ll1iBrGFBWwltkyewwhiswHFp26aDWaLCEhKXGs+DWazCKhKtM19 xg5icwrESFx8f4gd4g4NiQ03jzFBzBSUODnzCQuIzSwgL9G8dTYzyGIJgcdsEg23G6AaXCRu T5jJBGELS7w6vgUqLiPxf+d8JoiGdkaJNZNes0M4PYwSm47eYYSospbou30RyOYAWqEpsX6X PkTYUWLO/0lsIGEJAT6JG28FIY7gk5i0bTozRJhXoqNNCKJaTWJH01ZGiLCMxNM1ChMYlWYh +WAWkg9mIaxawMi8ilE8tbQ4Nz212DAvtVyvODG3uDQvXS85P3cTIzAZnP53/NMOxq+Xkg4x CnAwKvHwMqR8ihViTSwrrsw9xCjBwawkwpuq/TlWiDclsbIqtSg/vqg0J7X4EKM0B4uSOK/x opexQgLpiSWp2ampBalFMFkmDk6pBsb58f/fJIrqyzRnrnfRXHFaUs/lrnJb9c4XTbdfB8y2 /muf83+XbaPMzk2RMrP+9x1zu/08d8dzoScpV1uYDx7hEpVin/d8lq0Dp5OBzOSz9n9ar+a/ io3Y1d4cxXVt+YRVnvyzbzHsWq68s7llo8QVi63fEtM7drcVlpbNezOt/EHy5Fn3HT8qsRRn JBpqMRcVJwIAV496JwIDAAA= X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpikeLIzCtJLcpLzFFi42I5/e/4Pd2imM+xBvsmCFocbH7I5MDoserg B6YAxig9m6L80pJUhYz84hJbpWhDCyM9Q0sLPSMTSz1DY/NYKyNTJX07m5TUnMyy1CJ9uwS9 jHeTdzAXvOCu+PpUrIFxBlcXIyeHhICJxPbVu1m7GLk4hASWMkrc3vCQCSIhI/Hpykd2CFtY 4s+1LjaIom4miaZjuxkhnDOMEhPezWeHcC4wSlxuaQNr4RUwlPhz6RIziC0sYCuxZfIcRhCb DSg+ddNsMFtEQFLiWvNpMJtFQFWibe4zsF5OgRiJi+8PQQ3dwCix/uAGNpAEs4CmROv231A3 aUhsuHmMCWKZoMTJmU9YIGrkJZq3zmaewCg0C0nLLCRls5CULWBkXsUoklpanJueW2yoV5yY W1yal66XnJ+7iREY/tuO/dy8g/HSxuBDjAIcjEo8vAwpn2KFWBPLiitzDzFKcDArifCman+O FeJNSaysSi3Kjy8qzUktPsRoCvTRRGYp0eR8YGzmlcQbmhqaW1gamhubG5tZKInzdggcjBES SE8sSc1OTS1ILYLpY+LglGpglIvO3uzV/OOclLSIRy170FLV43ujt69c+5ztxuttCzuTQh5E hHbZVL1/lvqp+f3FjRcPH5Zo6jlxZ6pVWvvy5cfCPhVtWRv6V24xv3HoXrldIXeTLDmrT354 p/8qzHmFBG+j3VOWr2JRZ3ayei36m7lwouPDA12PD27cuv+G0t3Al0xHy3c+KlNiKc5INNRi LipOBABXIJgOlQIAAA== X-CMS-MailID: 20191213094002eucas1p27d133b1e2ec9c007e27cad47043df0f4 X-Msg-Generator: CA Content-Type: text/plain; charset="utf-8" X-RootMTR: 20191212182957epcas5p48645aa560e781ac1c34f00662a6d6176 X-EPHeader: CA CMS-TYPE: 201P X-CMS-RootMailID: 20191212182957epcas5p48645aa560e781ac1c34f00662a6d6176 References: <2022943386.989309814.1576175339554.JavaMail.root@zimbra62-e11.priv.proxad.net> On Thu, 2019-12-12 at 19:28 +0100, Antoine C. wrote: > Hello, >  > I finally found the cause of the frequent crashes I reported one > year ago ( https://protect2.fireeye.com/url?k=605d4b55-3d89f611-605cc01a-0cc47a31381a-5ceba38dc2a22d2c&u=https://www.zsh.org/mla/workers/2019/msg00059.html ). >  > This is due to malloc calls from signal handler, for instance: >  > #0  tcache_get (tc_idx=17) at malloc.c:2943 > #1  __GI___libc_malloc (bytes=296) at malloc.c:3050 > #2  0x000055c2217b27b5 in malloc (size=8) at ./main.c:255 > #3  0x000055c2218166f9 in zalloc (size=8) at mem.c:966 > #4  0x000055c221806da2 in addbgstatus (pid=11959, status=0) at jobs.c:2192 > #5  0x000055c2218478e7 in wait_for_processes () at signals.c:583 > #6  0x000055c221847cdc in zhandler (sig=17) at signals.c:648 > #7   > #8  0x00007f8895b69209 in __GI___sigsuspend (set=0x7ffe759b7160) at ../sysdeps/unix/sysv/linux/sigsuspend.c:26 > #9  0x000055c221847376 in signal_suspend (sig=17, wait_cmd=1) at signals.c:393 > #10 0x000055c2218054e8 in waitforpid (pid=11953, wait_cmd=1) at jobs.c:1551 > #11 0x000055c221807a10 in bin_fg (name=0x7f8896af4798 "wait", argv=0x7f8896af4830, ops=0x7ffe759b75c0, func=4) at jobs.c:2371 The main shell is suspended, waiting for a child to finish, so the fact it's in the signal handler isn't saying anything. >From the look of it, some memory corruption must already have occurred at this point to get the malloc to fail. pws