> BTW: it does not seem to be a problem with mutex/cond: I "saved" > those in an array for reuse (instead of calling _init()/_destroy() > for every invocation) and even then the size grows. I'll try to > build a debugging version of libc (with some malloc checks) over > the weekend.
Another old trick is to let your program eat memory for a good while, and then break into its execution. Randomly inspect some of the allocated memory your program still holds; there is a very good chance you're looking at leaked structures. Hopefully you can figure out what those structures are, and track down what's allocating so many. --david
