Marshall Clow (email@hidden) on Wed, Oct 13, 2004 15:11 said:
>I want to find leaks in my program. (Built with CW 9.3, Mach-O, MSL).
You might take a look at DebugNew, part of CW. Though beware new/delete
become thread-unsafe if you use it.
Also an MW employee (Howard Hinnant) has written a similar piece of code:
<http://home.twcny.rr.com/hinnant/MemoryManager/>
more info here:
<http://groups.google.ca/groups?hl=en&lr=&threadm=hinnant-
email@hidden&rnum=1&prev=/groups%3Fq%3Dhttp:/
/home.twcny.rr.com/hinnant/MemoryManager/
%2Bthread%2Bsafe%26hl%3Den%26lr%3D%26selm%3Dhinnant-
0111002315080001%2540ith3-464.twcny.rr.com%26rnum%3D1>
>I tried MallocDebug. No joy. It tried to launch the app, and
>eventually gave up, complaining that it couldn't read from (null).
This has come up many many times. Some apps built with CW are not liked
by MallocDebug. It has been discussed on the Carbon list and
comp.sys.mac.programmer.* You might try using BSD C instead of MSL C
(problems with duplicate symbols otherwise), or maybe just make sure to
set the export symbols to none.
hth,
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Mac Software Designer Montréal, Québec, Canada
_______________________________________________
Do not post admin requests to the list. They will be ignored.
PerfOptimization-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/perfoptimization-dev/email@hidden
This email sent to email@hidden
