[kman42]

I have an application that I think is slowly leaking memory. It runs great for a about an hour and then quits unexpectedly. Does MallocDebug allow me to watch the memory allocation for various objects? Can someone give me a quick primer to get me started? I don't have a clue what I am doing, but I launched the app and tried Attach... but it told me there were no apps running with attach code or something. Any help would be appreciated.

thanks,
kman

[kman42]

Okay, I read the help to get me started. I chosed my app and hit launch. It crashes immediately even though this doesn't happen when I launch the app by itself. Here's the crash dialog from Malloc:

/F@HMonitor/build/F@HMonitor.app/Contents/MacOS/F@HMonitor accessed memory at 0x7c0802ae illegally.

kman

[smeger]

MallocDebug turns on some extra debugging options that try to make malloc crash immediately if there's a problem with your code. The reason for this is that memory errors usually suck to track down since the crash will often take place very far from the problem (it took me 5 eight hour days to track one of these down last week).

From the command line, do something like this:

Code:
% cd <path to your executable>/Contents/MacOS/<your executable name>
% gdb <your executable name>
(gdb) set env MallocScribble 1
(gdb) set env MallocGuardEdges 1
(gdb) set env MallocStackLogging 1
(gdb) set env MallocCheckHeapStart 1000
(gdb) set env MallocCheckHeapEach 1000
(gdb) run

<your code will crash after spewing out some messages>

(gdb> bt

This'll show you where your code is dying. More info here.