It may be the case that the malloc scene is confused and lacks standards, but the ability to debug leaks with a simple test like this has been a long standing and very serious problem with Objective C, to the point that I have my doubts there is any significant size program written in the language that is not silently leaking like a sieve.
This solution at least works in all the environments that are of interest to my company, and if others can figure out extensions to this simple API to make it work with some of the other ad-hoc malloc and pseudo-malloc API's, its all to the advantage of everyone. Feel free to take the code I posted and extend as needed, or to simply use it to help you track down your own memory leaks. -- +---------------------------------------------------------------+ | Dale Amon Immortal Data | | CEO Midland International Air and Space Port | | a...@vnl.com "Data Systems for Deep Space and Time" | +---------------------------------------------------------------+ _______________________________________________ Discuss-gnustep mailing list Discuss-gnustep@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnustep
