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=DKIM_ADSP_CUSTOM_MED, FREEMAIL_FROM,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 27574b8f for ; Fri, 13 Dec 2019 09:46:11 +0000 (UTC) Received: (qmail 3370 invoked by alias); 13 Dec 2019 09:46:07 -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: 45013 Received: (qmail 16464 invoked by uid 1010); 13 Dec 2019 09:46:06 -0000 X-Qmail-Scanner-Diagnostics: from mail-il1-f172.google.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(209.85.166.172):SA:0(-2.0/5.0):. Processed in 1.233735 secs); 13 Dec 2019 09:46:06 -0000 X-Envelope-From: roman.perepelitsa@gmail.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.166.172 as permitted sender) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=pCsRmFibtlJmojfXNhLIXhHN18tpSSgdBAWUMjAVTAU=; b=H1lPdMXqRFpUOwox9AT8PV19FWIm8uaFyOeX/N0DKErg3GS47l4h6hJTeLe2w7OKnI Sj22yl5bgwzeJ68QslQhvhOpV24aQp+lPqfKGClxks5W+I5hdxC9JJBTZ+uJ8mb8BANT N1dffsKlBhoXsWITUj9C2elZr2e7I0NXOLCG3DS2lXsK4uoexOB6y/tYSL+B7DxW7O12 2BPnO1w5+PQcEJjEtUh7TcyIAcOVWs7HUYM28VMaxScWgfgyOdP0H7l2GDkKePNguRV7 qwwHx1gtMOy/zLmnSgwFj20se3Ey0lssTqI9F+QcsDBxa2F/KdORdqMJxLLfMq7uYy03 UR3g== X-Gm-Message-State: APjAAAWHtBbY3C0T7DyWx0KHwxlK9mLCbumyR36Q8qRz+Hbgvr/f+6Sp sbYEXc7MotHhfKA4/R3lxer5mOAPngONbw21UMU= X-Google-Smtp-Source: APXvYqzptWsdECPZbDM5YVSHu7KD2oObosyuM6orfVQ9SyTlB2Ljd4Qc1CNdSUhBKBsvjvscpqW2lAo1ExjOfwUdq/o= X-Received: by 2002:a92:6603:: with SMTP id a3mr1116775ilc.168.1576230332018; Fri, 13 Dec 2019 01:45:32 -0800 (PST) MIME-Version: 1.0 References: <2022943386.989309814.1576175339554.JavaMail.root@zimbra62-e11.priv.proxad.net> <1576230001.5214.1.camel@samsung.com> In-Reply-To: <1576230001.5214.1.camel@samsung.com> From: Roman Perepelitsa Date: Fri, 13 Dec 2019 10:45:21 +0100 Message-ID: Subject: Re: [BUG] Crash due to malloc call in signal handler To: Peter Stephenson Cc: Zsh hackers list Content-Type: text/plain; charset="UTF-8" On Fri, Dec 13, 2019 at 10:40 AM Peter Stephenson wrote: > 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. malloc is not async signal safe. It's illegal to call it from a signal handler. I'm not saying this is what's causing a crash. Roman.