On Fri, Mar 31, 2006, David Higgs wrote: > 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.
Do you know how to find the allocated memory? Is there some "map" (linked list?) to access from the debugger? PS: please note that this leak doesn't show up on four other OSs, not even testing with Purify shows a leak. Hence it seems most likely that the leak is somewhere in an OpenBSD library, which means I wouldn't find any of "my" structures on the heap (except for those that are still in use).
