On 3/30/06, Claus Assmann <[EMAIL PROTECTED]> wrote: > Is there some "simple" way to find a memory leak in some OS supplied > library? I have a (constantly running) application that grows in a > week from 5MB to 15MB in size (VSZ and RSS as reported by ps). The > application can be compiled with an optional debugging memory > allocator that tracks all (de)allocations to check whether any of > its malloc()/free() calls leak memory; according to that tool the > application behaves fine. Hence I'm wondering whether there is a > memory leak in some library or the OS, which also could be triggered > by the way my application uses it (see the recent thread about > telldir()/seekdir()). My application uses pthreads and the DNS > resolver, the latter by contacting it via UDP: sendto(), recvfrom(). > Note: the memory leak seems to be unique to OpenBSD (3.8 and earlier), > I can't reproduce it on SunOS 5.9 and others. That's why I'm asking > for hints where to look for the leak: is there some "simple" way > to show the allocated memory in the debugger or via system calls > and to find out which functions made those allocations?
particular to pthreads, if you are using mutexes or somesuch on the stack, you will leak memory. (the lock on the stack is just a pointer, it gets allocated on first use).
