From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,4a5f04fa4207fc8e X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-08-25 10:56:08 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!news.tele.dk!small.news.tele.dk!194.25.134.62!newsfeed00.sul.t-online.de!t-online.de!news-lei1.dfn.de!news-nue1.dfn.de!news-han1.dfn.de!news.fh-hannover.de!news.cid.net!news.enyo.de!news1.enyo.de!not-for-mail From: Florian Weimer Newsgroups: comp.lang.ada Subject: Re: memory pool for entire ada program Date: Sat, 25 Aug 2001 20:14:36 +0200 Organization: Enyo's not your organization Message-ID: <87y9o86m7n.fsf@deneb.enyo.de> References: <9m5jod$o8o$1@ns.omskelecom.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Xref: archiver1.google.com comp.lang.ada:12415 Date: 2001-08-25T20:14:36+02:00 List-Id: "Dmitriy Anisimkov" writes: > I need to know where is the memory leak, > in the ada code or in the C library, used in my program. GNAT uses the vendor C library malloc(). Many malloc() implementations provide hooks which you can use to implement your tracing routines. If you're working on a GNU system, you might want to have a look at /usr/include/execinfo.h, for obtaining stack backtraces.