Any tips for hunting down memory leaks in the kernel? Is debugalloc.c a replacement for the libc allocator?
I haven't narrowed it down yet, but /dev/swap reports growth after each exec, but not after each fork (in xen, not the standard pc kernel). ^T^Tx also shows growth:
122 holes free 00c53e80 00c57ea8 16424 00d20018 00d24040 16424 00e149a0 00e14bc0 544 00e7cca0 00ec0f48 279208 01015c90 010165d0 2368 011bb468 0217d000 16522136 16837104 bytes free ialloc 0/14045184 pad 0, concat 0, pullup 0, copy 0 consume 0, produce 72, qcopy 1732024 Main max 22673044 cur 1835456 free 119392 alloc 53937312 Image max 16777216 cur 0 free 0 alloc 0 3096/16003 memory 0/130800 swap 0 iolist
$ echo
122 holes free 00c53e80 00c57ea8 16424 00d20018 00d24040 16424 00e149a0 00e14bc0 544 00e7cca0 00f79678 1034712 01015c90 010165d0 2368 011bb468 0217d000 16522136 17592608 bytes free ialloc 0/14045184 pad 0, concat 0, pullup 0, copy 0 consume 0, produce 80, qcopy 1781260 Main max 22673044 cur 1835456 free 119360 alloc 54047936 Image max 16777216 cur 0 free 0 alloc 0 3102/16003 memory 0/130800 swap 0 iolist
Tim Newsham http://www.lava.net/~newsham/
