Re: MallocDebug: Can it be used at all?
Re: MallocDebug: Can it be used at all?
- Subject: Re: MallocDebug: Can it be used at all?
- From: Bob Stuller <email@hidden>
- Date: Thu, 14 Mar 2002 17:29:12 -0500
Jonathan, Greetings!
At 4:37 PM -0500 3/14/02, Jonathan Feinberg wrote:
At 11:38 AM -0800 3/14/02, Matthew Formica wrote:
I don't think I've ever seen MallocDebug lie. In this case, I bet your app
is interacting in a weird way with Unsanity products (WindowShade/X, etc.) -
try disabling them.
I am not using those products.
As I've said, I cannot open *any*application with MallocDebug; it
always gives the same crash message. Furthermore, it will not allow
me to attach to any running process, saying that no applications are
running which were compiled with libMallocDebug. Yet the docs (such
as they are) for MallocDebug imply that it's only necessary to
dynamically link with the system framework in order to use it.
If I *wanted* to statically link my app with libMallocDebug, and
avoid dynamically linking with the usual runtime, how would I do so?
I am quite at the end of my rope.
This may have some relevance, or it may not, because I am using
MallocDebug with a CFM app rather than a Cocoa app. That said, here
is the stuff that I paste into a Terminal window to begin a
MallocDebug session. I do this before letting MallocDebug attach to
the program. This still works for me: It might be worth a try.
gdb /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp
set start-with-shell 0
set env DYLD_INSERT_LIBRARIES /usr/lib/libMallocDebug.A.dylib
set env DYLD_FORCE_FLAT_NAMESPACE 1
run /path/to/my/app
<<
hth
Peace,
Bob
--
It is no use to preach to [children] if you do not act decently yourself.
- Theodore Roosevelt
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.