From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6848 invoked by alias); 11 Feb 2014 18:27:45 -0000 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 Received: (qmail 6832 invoked by uid 89); 11 Feb 2014 18:27:44 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-4.4 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 11 Feb 2014 18:27:43 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s1BIRfG8031790 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 11 Feb 2014 13:27:42 -0500 Received: from host2.jankratochvil.net (ovpn-116-93.ams2.redhat.com [10.36.116.93]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s1BIRbwo021129 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 11 Feb 2014 13:27:39 -0500 Date: Tue, 11 Feb 2014 18:27:00 -0000 From: Jan Kratochvil To: Florian Weimer Cc: gdb@sourceware.org, Tom Tromey Subject: Re: How important is mcheck? Message-ID: <20140211182737.GA17519@host2.jankratochvil.net> References: <52F8F53C.8090708@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52F8F53C.8090708@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes X-SW-Source: 2014-02/txt/msg00030.txt.bz2 On Mon, 10 Feb 2014 16:50:20 +0100, Florian Weimer wrote: > Could you move mcheck in-tree? IMO mcheck has been obsoleted by asan (=gcc -fsanitize=address). I just do not run GDB regularly under asan yet as in that case one can no longer use 'ulimit -v 1000000' to catch GDB memory runaways. ERROR: AddressSanitizer failed to allocate 0x400000000 (17179869184) bytes at address 0x00067fff8000 (12) ReserveShadowMemoryRange failed while trying to map 0x400000000 bytes. Perhaps you're using ulimit -v Unfortunately 'ulimit -m' (=RSS) has no effect so one has to give up on the memory limit for GDB. But it should be worth the asan improved checks. Jan