Use tools - device leaks

I'm starting to use leak tools with iPhone 3G. When I try to run the application using tools on the iPhone, I get

Target failed to run: Remote exception encountered: 'Failed to get task for pid 280' 

Ideas?

The only time when I manage to start the application with the tools, it works very slowly, I could not test it. What are the steps to launch an application on a device that is looking for leaks?

+55
ios memory-leaks instruments
Dec 01 '10 at 10:30
source share
4 answers

The solution for me was to make sure that my debug configuration was used in my profile scheme, not release.

In Xcode 4, select โ€œProduct / Edit Schemeโ€ from the top menu, then click the โ€œProfileโ€ button on the left. In the "Information" panel, you will see the "Assembly Configuration" setting to "debug"

+146
Mar 28 '11 at 10:43
source share

This error also occurs if you try to test your application on a device with a selected distribution profile. Make sure you have the correct code settings for your development.

+28
Mar 23 '11 at 2:11
source share

You CAN profile the release version on the device. What you need to do is build the release build using a developer certificate. See here .

+6
Mar 21 '12 at 16:09
source share

Tools basically do their job, becoming a debugger for the application. If you cannot run the Xcode debugger against it, you cannot run the tools against it.

Basically, rights should be set to allow debugging.

Sometimes after using Xcode to debug applications, I find that I canโ€™t use Tools until I reboot the device.

Unlike Xcode, tools can be confused between two applications with the same name, but with different package identifiers. (Or, possibly, the same name and similar package identifiers.) When I have several versions of an application on a device, I often have to remove unnecessary ones to make Tools connect to the correct application. If you have one debug build and one release build, this can be a problem.

So, remove all duplicate applications and restart the device. (You can change the display name for release and debug configurations.)

0
Feb 14 '13 at 7:49
source share



All Articles