From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18630 invoked by alias); 17 Jun 2017 05:07:48 -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: 41313 Received: (qmail 22927 invoked from network); 17 Jun 2017 05:07:47 -0000 X-Qmail-Scanner-Diagnostics: from mail-ua0-f180.google.com 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(209.85.217.180):SA:0(-0.0/5.0):. Processed in 2.04695 secs); 17 Jun 2017 05:07:47 -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.0 required=5.0 tests=RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_PASS,T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: schaefer@brasslantern.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.217.180 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:date:in-reply-to:comments:references:to:subject :mime-version; bh=g50pMoCRaea4rnWE4JCiXNBJPRbj5cQMZrJb1Bc6cjo=; b=R4pUjByymc2zri44di6UxaWP6R/m4qyWtE/tRijNYfF456fEYI1eFHfXYFpU/TCk4b Q8Q/Jhtm5Wthp3vXJ/UFZ52kjobj0URdRiE6Npqk/r3+40TAvR1ZvfYnQs8z9527XJtq 9fZzfVrX4eEO4LWEhkqZCFSmWn7AAknBUFL4xDHCEnlfhVMQPJBEHbeR51uo0YjXjjY/ cr0ARdF2hmzM7Pr3uM8muj1XdDhSdHNjh5pmYecTT9s4zvemh+qu4hCx2WKKzgvBctni jd9wRTbo23qRO3wrV5+ANPoVwD0VYl3EVdUr7DCCc9E5wyW30aTddkH42mp1y/aK0M0B l1WQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version; bh=g50pMoCRaea4rnWE4JCiXNBJPRbj5cQMZrJb1Bc6cjo=; b=rImix8ZEvwNj/5uZLnRB0XBuN/bPkoDylFID5YX0K38EYC5eWNxrtm+yQ7297oEazX VcCRV0P9ptW2Xoey35LSIXr/d+X0QS6KvIPQBRFkoZyl9L9rGWsogFuid4Q9eYfl5Fh1 XYmAlbkTzgsUt89wTYtOJzyJaTfA7DMSLaTt9vdYsii8vA2B9yNNl0jl52Uq/z1b+XGy Cqdub+Nl+TzFBLkzO6b40drvR+WXjtd8rvuGZkUywa1U0235Jhq22E0ruPIdQWQmnH4J 9KSpl3v/2JQsk8DKuS/QUdDNEjDwC8p2HxJ1UqETUhg0unKGPLIk6wgZt8ifwIjGvnf9 RhzQ== X-Gm-Message-State: AKS2vOwP0kDXxft3vetYluWBs6RJtNejeijHI4SOZGDPtMWURy5VY3rU 0YrKsRDVAnHltjprAZo= X-Received: by 10.176.6.105 with SMTP id f96mr9097900uaf.15.1497676058683; Fri, 16 Jun 2017 22:07:38 -0700 (PDT) From: Bart Schaefer Message-Id: <170616220824.ZM28272@torch.brasslantern.com> Date: Fri, 16 Jun 2017 22:08:24 -0700 In-Reply-To: Comments: In reply to Sebastian Gniazdowski "Valgrind automatic tests, ran for almost every Zsh test and zredis" (Jun 16, 5:14pm) References: X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: Valgrind automatic tests, ran for almost every Zsh test and zredis MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Jun 16, 5:14pm, Sebastian Gniazdowski wrote: } } ============ The maybe-suspicious reports ============ A few of these look like they're probably the same report reached via slightly different script paths. The backtraces aren't very helpful without knowing which specific test case set them off. I'm guessing most of these are going to turn out to be from a subshell exec'ing or exiting without bothering to clean up allocations done by the parent, particularly in the case where the leaked memory is from the stdio library (indicating "FILE *bshin" was never fclose()d).