How to use MallocStackLogging on the device? How to use MallocStackLogging on the device? xcode xcode

How to use MallocStackLogging on the device?


Here is how I debug APP with malloc stack history on idevice, it's really complicate, but I have no other way to deal with an auto release pool memory problem.

  1. You need A jailbreak idevice with developer tools installed, then you have gdb.

  2. To enable malloc stack loggin, you need set environment variables MallocStackLoggingNoCompact and MallocStackLogging, we need some trick to do it.

First, we need grant your app root privilege.

 mv -f /User/Application/xxxxxxxxxxxxx/YOUR_APP.app /Application/YOUR_APP.app cd /Application chown -R root:wheel YOUR_APP.app chmod 4755 YOUR_APP.app/YOUR_APP

Rename your program

mv YOUR_APP.app/YOUR_APP   YOUR_APP.app/BACK_UP_NAME

Use a short shell scrip to start your program, so we can keep the env. Save it to YOUR_APP.app/YOUR_APP

#!/bin/bashexport MallocStackLogging=1export MallocStackLoggingNoCompact=1exec /Applications/YOUR_APP.app/BACK_UP_NAME

Done.

Just start you app, touching on the icon or use open command, you'll see a stack log file in /tmpdirectory.

Use ps aux | grep YOUR_APP find process id, gdb -p PROCESS_ID attach to the progress, make a breakpoint, try info malloc ADDRESS, malloc history will show up.


In the Instruments application, which can diagnose an app running in the simulator or on a device, the Allocations instrument records memory addresses and allocation histories. You can browse by object/allocation type or specific memory address. This is likely the most straightforward way to accomplish what you want.

Running malloc_history on the device would require either jailbreaking to enable an ssh connection to the device, or running malloc_history from within your code. But I am not certain whether malloc_history exists on an iOS device. And malloc_history's help text does not mention an option for operating on log files rather than an existing process, which you likely already know.


I don't mean to sound flippant, but have you tried plugging the device in and running it under the debugger whilst connected ?

I do extensive debugging whilst runnning the application on the device. You do need to start the application under the debugger.