This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Bug?: g++, memusage reports memory leak with an empty programm


Hi!

I compiled the following programm and started it using memusage. The result were 116 bytes allocated and not freed.

memtest.cpp
 int main() {}  // Empty program, does nothing

Compiled with
g++ memtest.cpp -o memtest

memusage ./memtest

Here memusage reports 116 bytes that were allocated but not freed. On another machine the value was not 116 but 64. So this doesnt seem to be a constant.

I tested with gcc 3.1 and gcc 3.2 20020903, on Debian and Suse, with memusage and valgrind, always some bytes lost.

Is this a bug or can this "leak" be ignored?

thx,

Christoph


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]