From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5944 invoked by alias); 11 Jan 2012 14:31:59 -0000 Received: (qmail 5932 invoked by uid 22791); 11 Jan 2012 14:31:57 -0000 X-SWARE-Spam-Status: No, hits=-7.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 11 Jan 2012 14:31:36 +0000 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q0BEVYwd009169 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 11 Jan 2012 09:31:34 -0500 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q0BEVYF9016144; Wed, 11 Jan 2012 09:31:34 -0500 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id q0BEVX2T010288; Wed, 11 Jan 2012 09:31:33 -0500 From: Tom Tromey To: Jan Kratochvil Cc: Khoo Yit Phang , gdb@sourceware.org Subject: Re: xfree/make_cleanup memory leak pattern? References: <197CEDA3-0851-4FD2-B821-FD800C991F2D@cs.umd.edu> <20120111003035.GA11850@host2.jankratochvil.net> <20120111003215.GA11968@host2.jankratochvil.net> Date: Wed, 11 Jan 2012 14:31:00 -0000 In-Reply-To: <20120111003215.GA11968@host2.jankratochvil.net> (Jan Kratochvil's message of "Wed, 11 Jan 2012 01:32:15 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.92 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2012-01/txt/msg00039.txt.bz2 >>>>> "Jan" == Jan Kratochvil writes: Jan> Yes, I agree. immediate_quit is not well handled. I think it is only used in selected spots. I wonder if we could enhance the exception checker to look for problems in this area. Tom