From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18314 invoked by alias); 10 Feb 2017 18:32:38 -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: X-Seq: 40519 Received: (qmail 9383 invoked from network); 10 Feb 2017 18:32:38 -0000 X-Qmail-Scanner-Diagnostics: from park01.gkg.net by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(205.235.26.22):SA:0(0.5/5.0):. Processed in 0.711258 secs); 10 Feb 2017 18:32:38 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=0.5 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, RCVD_IN_SORBS_SPAM,RP_MATCHES_RCVD,T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.1 X-Envelope-From: SRS0=9f3d=ZY=brasslantern.com=schaefer@bounces.park01.gkg.net X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at bounces.park01.gkg.net does not designate permitted sender hosts) X-Virus-Scanned: by amavisd-new at gkg.net Authentication-Results: amavisd4.gkg.net (amavisd-new); dkim=pass (2048-bit key) header.d=brasslantern-com.20150623.gappssmtp.com X-Greylist: from auto-whitelisted by SQLgrey-1.8.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=resent-from:resent-message-id:resent-date:resent-to:from:message-id :date:in-reply-to:comments:references:to:subject:mime-version; bh=XjisKAMTzsX8Hz0r7paFwWUTfJvccZMrX91BGM4auxo=; b=oAIvzvE6CqDwiJ0OuN2Wu/mjvzFJUwO5nQw4+Ot+xxw+6Krm0hvBWtLm5wkjXESbal NKPQcN1ruoUcXtEh43jazLXLdv7nRW2pOFFAeuARBl7Q8n4pdEma0qm+itS0fT9B2A6a GM0KJGsZZxSfr79Io3Yg2XqPCjeJAvfPFfcaX5JG79xybi3IPNJKtHtbjYxMM1F+d/CR ha7rQtBWi1gce6Ez7fcJ7HU4NHt5aDR28KrHZmlqtrSI1v/J5wXtE0Qbg7aT9tY7LLo9 CLUZaZptBcO2SeQXQNi/YH1KIEpSy08rAdy/ND/ZkxxUa4vkkVPmBJ0VsQImgx4z5a63 vLtg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:resent-from:resent-message-id:resent-date :resent-to:from:message-id:date:in-reply-to:comments:references:to :subject:mime-version; bh=XjisKAMTzsX8Hz0r7paFwWUTfJvccZMrX91BGM4auxo=; b=OU5JKhi9LrEf2QH9YuL/WpVYMtIzGBXd9cqNCK7628wgjT0Nf494OgPmWoJOPNSBYR jC7H9QTD6I4hQPjR20kTGYQDvLoLtotJdXQwGkmAeJkdeCdNR/OM0LkJXEvFlyUAJ7GM PbkmOKHaCui17pO9EOuvCnKKJfYf310d5I+/682Bh1PyJKYLzS5D667t1+1AO3UZUGKg 9BJIQj0omOSyCVCyuSAlIMzo1dt1dSgP1kxWMBGbdJgyY7fxQd7cEbfG5A+Q93fCy0Hw Ppd/lX88Pp2T0ikclFk1tkzOFu3CeDbFklL4dx7fJMXllSqjA3tCVeFQA3LwzD3y7KUb 5ebA== X-Gm-Message-State: AMke39lFVnVr49nnpOdl8Hc5/IBqVA+l4VCfJeHd5e4nlJNt9OFgbVdfWDSMC1n6ox+K+w== X-Received: by 10.159.36.165 with SMTP id 34mr5511983uar.48.1486751213011; Fri, 10 Feb 2017 10:26:53 -0800 (PST) Resent-From: Bart Schaefer Resent-Message-Id: <170210102709.ZM28988@torch.brasslantern.com> Resent-Date: Fri, 10 Feb 2017 10:27:09 -0800 X-Mailer: OpenZMail Classic (0.9.2 24April2005) Resent-To: zsh-workers@closedmail.org From: Bart Schaefer Message-Id: <170210102523.ZM28915@torch.brasslantern.com> Date: Fri, 10 Feb 2017 10:25:23 -0800 In-Reply-To: <1486729474.1489636.876722008.7B4EC1FC@webmail.messagingengine.com> Comments: In reply to Sebastian Gniazdowski "When is mem.c / malloc called?" (Feb 10, 4:24am) References: <1486729474.1489636.876722008.7B4EC1FC@webmail.messagingengine.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: When is mem.c / malloc called? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Feb 10, 4:24am, Sebastian Gniazdowski wrote: } } ... compiled once without --enable-zsh-mem, once with it. Then in a } module I've called zshcalloc() and malloc(). Didn't get the message. --enable-zsh-mem should turn on the internal malloc, see line 1026 of mem.c. However, if you didn't relink separately-compiled modules, they might still link at runtime to the system malloc. } I'm writing a module that needs thread safe memory allocation. This sounds pretty dangerous, as the rest of zsh (signal handling in particular, update of the environment on e.g. "export", etc.) is not going to be thread-safe.