From: Daniel Jacobowitz <drow@false.org>
To: Fabian Cenedese <Cenedese@indel.ch>
Cc: gdb@sourceware.org
Subject: Re: Memleaks?
Date: Mon, 30 Oct 2006 15:08:00 -0000 [thread overview]
Message-ID: <20061030150832.GA9090@nevyn.them.org> (raw)
In-Reply-To: <5.2.0.9.1.20061030155937.0185e010@NT_SERVER>
On Mon, Oct 30, 2006 at 04:04:26PM +0100, Fabian Cenedese wrote:
> (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.
I've no idea; probably not.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-10-30 15:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 11:41 Memleaks? Fabian Cenedese
2006-10-30 13:45 ` Memleaks? Daniel Jacobowitz
2006-10-30 15:06 ` Memleaks? Fabian Cenedese
2006-10-30 15:08 ` Daniel Jacobowitz [this message]
2006-10-30 16:02 ` Memleaks? Fabian Cenedese
2006-10-30 20:37 ` Memleaks? Michael Snyder
2006-10-31 7:27 ` Memleaks? Fabian Cenedese
2006-10-31 12:16 ` Memleaks? Christopher Faylor
2006-11-02 7:31 ` *SPAM*Re: Memleaks? Fabian Cenedese
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061030150832.GA9090@nevyn.them.org \
--to=drow@false.org \
--cc=Cenedese@indel.ch \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox