From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id 76QmKvJlbGAQTwAAWB0awg (envelope-from ) for ; Tue, 06 Apr 2021 09:45:22 -0400 Received: by simark.ca (Postfix, from userid 112) id 9EAA91E939; Tue, 6 Apr 2021 09:45:22 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=0.7 required=5.0 tests=DKIM_SIGNED,MAILING_LIST_MULTI, RCVD_IN_BL_SPAMCOP_NET,RDNS_DYNAMIC,T_DKIM_INVALID,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.2 Received: from sourceware.org (ip-8-43-85-97.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id D572C1E54D for ; Tue, 6 Apr 2021 09:45:21 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 7782D3846078; Tue, 6 Apr 2021 13:45:21 +0000 (GMT) Received: from gateway21.websitewelcome.com (gateway21.websitewelcome.com [192.185.45.154]) by sourceware.org (Postfix) with ESMTPS id 51AE63846078 for ; Tue, 6 Apr 2021 13:45:18 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 51AE63846078 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=tromey.com Authentication-Results: sourceware.org; spf=fail smtp.mailfrom=tom@tromey.com Received: from cm10.websitewelcome.com (cm10.websitewelcome.com [100.42.49.4]) by gateway21.websitewelcome.com (Postfix) with ESMTP id DD61F400DDB63 for ; Tue, 6 Apr 2021 08:45:17 -0500 (CDT) Received: from box5379.bluehost.com ([162.241.216.53]) by cmsmtp with SMTP id Tm17lJrIqL7DmTm17ldcBY; Tue, 06 Apr 2021 08:45:17 -0500 X-Authority-Reason: nr=8 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tromey.com; s=default; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=H62Tx/OXRVqaPeK849wjPN6nwwPuCtmSaA2DY27evLk=; b=fboll36N/YAdMDC6E9Qq7opg4V ZwKIkTElhKICDCJ+WegPu8dwdbCKMq7CWEANd8QR19K029Dlvfsi6mmcDpPTEk6bV8Qh1FO2AP2HW fw3cpek7dgAJprRbsDnYpAhDC; Received: from 71-211-182-15.hlrn.qwest.net ([71.211.182.15]:59720 helo=murgatroyd) by box5379.bluehost.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from ) id 1lTm17-0005HW-CJ; Tue, 06 Apr 2021 07:45:17 -0600 From: Tom Tromey To: Simon Marchi via Gdb-patches Subject: Re: [PATCH] sim/m32c: fix memory leaks in opc2c References: <20210405145856.3925296-1-simon.marchi@polymtl.ca> X-Attribution: Tom Date: Tue, 06 Apr 2021 07:45:16 -0600 In-Reply-To: (Simon Marchi via Gdb-patches's message of "Tue, 6 Apr 2021 09:28:59 -0400") Message-ID: <877dlfle6r.fsf@tromey.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - box5379.bluehost.com X-AntiAbuse: Original Domain - sourceware.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tromey.com X-BWhitelist: no X-Source-IP: 71.211.182.15 X-Source-L: No X-Exim-ID: 1lTm17-0005HW-CJ X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: 71-211-182-15.hlrn.qwest.net (murgatroyd) [71.211.182.15]:59720 X-Source-Auth: tom+tromey.com X-Email-Count: 1 X-Source-Cap: ZWx5bnJvYmk7ZWx5bnJvYmk7Ym94NTM3OS5ibHVlaG9zdC5jb20= X-Local-Domain: yes X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: gdb-patches-bounces@sourceware.org Sender: "Gdb-patches" Simon> I might try to take it on as a side project, but this is clearly too big Simon> as an immediate solution. What do you think of the patch below that Simon> sets ASAN_OPTIONS while running the tools? FWIW, I was surprised to hear that leak sanitizer reported this kind of leak. IIRC, valgrind has an option to ignore these, for just the reason that Mike pointed out -- there's no point to handling a leak just before exit. Anyway, I researched a little and came across this answer: https://stackoverflow.com/questions/51553115/how-do-i-make-leaksanitizer-ignore-end-of-program-leaks I don't know if that's something we'd want to enshrine in the tree, but at least now we know there's a way available if we want it. Tom