8 Apr
2010
8 Apr
'10
4:50 a.m.
2010/4/8 Daniel-Constantin Mierla <miconda(a)gmail.com>om>:
it does not look as a dump with memory debugging on.
SOrry, I just applied "MEMDBG=1" in one of the servers and got the
output in the other.
When memdbg is on, you should get something like:
0(17665) 1. N address=0xb5ab2440 frag=0xb5ab2428 size=4 used=1
0(17665) alloc'd from timer.c: init_timer(52)
Notice the "alloc'd ...' line which specifies the place where the memory
was
allocated.
A leak is signaled by many occurrences of allocation from same place
(skipping the part of allocation done for config parsing and module
initialization which happen only one, at startup).
Thanks a lot, understood now. I will check it periodically.
--
Iñaki Baz Castillo
<ibc(a)aliax.net>