From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32521 invoked by alias); 15 Nov 2010 22:34:05 -0000 Received: (qmail 32497 invoked by uid 22791); 15 Nov 2010 22:34:04 -0000 X-SWARE-Spam-Status: No, hits=-4.8 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (74.125.121.35) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 15 Nov 2010 22:33:22 +0000 Received: from hpaq7.eem.corp.google.com (hpaq7.eem.corp.google.com [172.25.149.7]) by smtp-out.google.com with ESMTP id oAFMXJsD017800 for ; Mon, 15 Nov 2010 14:33:19 -0800 Received: from iwn1 (iwn1.prod.google.com [10.241.68.65]) by hpaq7.eem.corp.google.com with ESMTP id oAFMRAJO024883 for ; Mon, 15 Nov 2010 14:33:18 -0800 Received: by iwn1 with SMTP id 1so8642199iwn.37 for ; Mon, 15 Nov 2010 14:33:17 -0800 (PST) Received: by 10.231.10.137 with SMTP id p9mr3834254ibp.186.1289860396702; Mon, 15 Nov 2010 14:33:16 -0800 (PST) Received: from coign.google.com ([216.239.45.130]) by mx.google.com with ESMTPS id gy41sm363809ibb.17.2010.11.15.14.33.14 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 15 Nov 2010 14:33:15 -0800 (PST) From: Ian Lance Taylor To: fabian.van.der.werf@altenpts.nl Cc: gcc-help@gcc.gnu.org Subject: Re: Are the gcc memory hooks sometimes bypassed? References: <20101115140000.09e99b26@mail.altenpts.nl> Date: Mon, 15 Nov 2010 22:42:00 -0000 In-Reply-To: <20101115140000.09e99b26@mail.altenpts.nl> (Fabian van der Werf's message of "Mon, 15 Nov 2010 15:00:00 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-System-Of-Record: true X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2010-11/txt/msg00175.txt.bz2 "Fabian van der Werf" writes: > For a c++ arm application I need to trace the memory allocations. To > do this I am using the gcc memory hooks. For now I am only printing > the allocations and deallocations, see code below. Those hooks are actually not part of gcc. They are part of glibc, which is a separate project. I don't know why the hooks aren't adding up for you, but the place to ask would be on a glibc mailing list. See http://sourceware.org/glibc/ . Ian