Skip to main content

How to use MallocStackLogging on the device?



I've a memory issue in an iPhone app that I'd like to debug with MallocStackLogging . The error involves the gyroscope so I have to debug on the device not the simulator.





I've set the MallocStackLogging environment variable and the iPhone properly records the mallock stack logs:







MyApp(1856) malloc: recording malloc stacks to disk using standard recorder

MyApp(1856) malloc: stack logs being written into /private/var/mobile/Applications/1FD1F8D2-5D30-4AA7-B426-C52FE20266DE/tmp/stack-logs.1856.MyApp.index

MyApp(1856) malloc: Please issue: cp /private/var/mobile/Applications/1FD1F8D2-5D30-4AA7- B426-C52FE20266DE/tmp/stack-logs.1856.MyApp.e8z3IL.link /tmp/







Now how can I work with them?





I can transfer them to the Mac using the Xcode Organizer. But what should I do with these two files?





  • stack-logs.1856.MyApp.index



  • stack-logs.1856.MyApp.e8z3IL.link







I tried moving the files in /tmp on the Mac and called:







$ malloc_history 1856 -all_events

malloc_history cannot examine process 1856 because the process does not exist.







Clearly, the malloc_history command looks for running processes on the local machine. I'm missing an option to specify the log file manually.





Is there any way to get this to work either directly working with Xcode on the (non-jailbroken) device or after transferring the logs to the Mac?


Comments

  1. 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.

    ReplyDelete
  2. Try this post. I hope it can help you http://marcocattai.posterous.com/xcode-debug-environment-variable

    ReplyDelete

Post a Comment

Popular posts from this blog

Slow Android emulator

I have a 2.67 GHz Celeron processor, 1.21 GB of RAM on a x86 Windows XP Professional machine. My understanding is that the Android emulator should start fairly quickly on such a machine, but for me it does not. I have followed all instructions in setting up the IDE, SDKs, JDKs and such and have had some success in staring the emulator quickly but is very particulary. How can I, if possible, fix this problem?