Hi All,
When running valgrind on the current xlinrad I get the
following report on lost memory:
==8510== IN SUMMARY: 17 errors from 10 contexts (suppressed: 19 from 1)
==8510==
==8510== malloc/free: in use at exit: 24,056 bytes in 319 blocks.
==8510== malloc/free: 691 allocs, 372 frees,
What is the meaning of lost memory ? Is it a part of
memory space that will eventually be swapped to disk?
Presumably there is no owner to it, will it just
accumulate until the next reboot ?
In valgrind's terminology, lost memory is synonymous with a memory
leak - memory which has been malloc'ed
Hello Ramiro,
xlinrad crashes under Debian Sarge and shows the following Segmentation
Fault debbuged with gdb. I send it to you just in case it gives you some
clues. Is the 890=0x37A port a parallel port register? What is it used
for under Linrad?
Linrad uses the parallel port to control
Leif writes the code C and assembly so for Leif this means if he does a
malloc, calloc, realloc, etc. and if he then no longer needs the memory,
he must do a free on the no longer used memory.
Bob
Richard Hosking wrote:
Lost memory is allocated when an object in C++ is created , but not
...and I distinctly recall from many many moons ago hearing both my
Introductory C and Advanced C instructors tell the class (several times)
that it was proper C programming practice to free ALL of our allocated
memory structures prior to exiting a program, otherwise bad things would
happen.
They
