From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25673 invoked by alias); 30 Oct 2006 15:06:17 -0000 Received: (qmail 25663 invoked by uid 22791); 30 Oct 2006 15:06:16 -0000 X-Spam-Check-By: sourceware.org Received: from mxout.hispeed.ch (HELO smtp.hispeed.ch) (62.2.95.247) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 30 Oct 2006 15:06:10 +0000 Received: from indel.ch (84-73-11-232.dclient.hispeed.ch [84.73.11.232]) by smtp.hispeed.ch (8.12.11.20060308/8.12.6/taifun-1.0) with SMTP id k9UF66ep028026 for ; Mon, 30 Oct 2006 16:06:06 +0100 Received: from FABI.indel.ch [192.168.1.91] by indel.ch [127.0.0.1] with SMTP (MDaemon.v2.7.SP5.R) for ; Mon, 30 Oct 2006 16:05:10 +0100 Message-Id: <5.2.0.9.1.20061030155937.0185e010@NT_SERVER> X-Sender: cenedese@NT_SERVER (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Mon, 30 Oct 2006 15:06:00 -0000 To: gdb@sourceware.org From: Fabian Cenedese Subject: Re: Memleaks? In-Reply-To: <20061030134510.GB5443@nevyn.them.org> References: <5.2.0.9.1.20061030123115.0185cec0@NT_SERVER> <5.2.0.9.1.20061030123115.0185cec0@NT_SERVER> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-MDaemon-Deliver-To: gdb@sourceware.org X-Return-Path: cenedese@indel.ch X-Virus-Status: Clean X-DCC-spamcheck-01.tornado.cablecom.ch-Metrics: smtp-06.tornado.cablecom.ch 1377; Body=1 Fuz1=1 Fuz2=1 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-10/txt/msg00297.txt.bz2 At 08:45 30.10.2006 -0500, Daniel Jacobowitz wrote: >On Mon, Oct 30, 2006 at 12:40:56PM +0100, Fabian Cenedese wrote: >> I admit that I used not a state-of-the-art gdb, but I don't think that >> this was changed recently. I'd be pleased if you can correct me. >> >> GNU gdb 6.2.50_2004-10-14-cvs > >This is two years old; I can't really speculate on what has changed >since then. It may be simple memory leaks, or it may be something more >complex. I tried a self-compiled gdb 6.5. This seems a lot better. http://img163.imageshack.us/img163/2033/gdbnomemleakcy3.gif GNU gdb 6.5 Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "--host=i686-pc-cygwin --target=powerpc-eabi". (gdb) file dragon.x Load new symbol table from "/data/gdb-6.5/gdb/dragon.x"? (y or n) y Reading symbols from /data/gdb-6.5/gdb/dragon.x... unknown symbol type 0x1e...done. (gdb) info symbol 0xbca60 CINOS1ms::AddTimer(long *) + 72 in section .text (gdb) info address CINOS1ms::AddTimer(long *) During symbol reading, struct/union type gets multiply defined: struct CINOSBusModule. During symbol reading, forward-referenced types left unresolved, type code 0.. Symbol "AddTimer__8CINOS1msPl" is a function at address 0xbca18. I'm just wondering about the warnings. Is this serious? The debug info in the symbol file is stabs. Thanks bye Fabi