User Profile

When I am trying to start malloc stack tracing either through the UI test bundle or the app directly, I get the following errors in the console. When it's set to live allocations only, it works when the app is launched directly, but still doesn't work when the app is launched for testing. Both the Run and Test schemes have Malloc Stack Logging enabled with Live Allocations Only. I tried the combination of not having it Test scheme vs having it in the test scheme, but nothing helps. Has anyone experienced this? Trying to evaluate the dirty memory of the app but having no stack trace doesn't help with the numbers. Please note I understand instruments, vmtracker and all can be used for memory debugging, but I am doing some advanced debugging using vmmap and heaps cli tools, so I need to use the memory graph which contains malloc stack logging. AppName(18844) MallocStackLogging: could not tag MSL-related memory as no_footprint, so those pages will be included in process footprint - (null) AppName(18844) MallocStackLogging: unable to create stack logs at /private/var/tmp/stack-logs.18844.101780000.AppName.8Tcn3b.index AppName(18844) MallocStackLogging: stack logging disabled due to previous errors. AppName(18844) MallocStackLogging: recording malloc and VM allocation stacks to disk using standard recorder AppName(18844) MallocStackLogging: unable to create stack logs at /private/var/tmp/stack-logs.18844.101780000.AppName.BsMID3.index