Re: Memleaks?

Fabian Cenedese
2006-10-31T07:27:20Z

At 12:37 30.10.2006 -0800, Michael Snyder wrote:
>On Mon, 2006-10-30 at 17:01 +0100, Fabian Cenedese wrote:
>> 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.
>>
>> Actually 6.5 behaves the same as 6.2.5. The difference was not the
>> version but the calling. When started with "gdb --readnow" every file
>> read will leave some memory behind and use more and more. So it
>> seems that the full symbols are not cleaned up as well as the partial
>> symbols.
>
>It's not at all surprising that that would make a difference.
>With --readnow, you're going to do an enormous amount of mallocing.

I don't mind the memory being used. I mind the memory not being freed
upon subsequently reading a new file. That's in my eyes the definition
of a memleak.

Can somebody test this on Linux to find out if it's gdb or maybe cygwin?

bye Fabi