ios-deploy
Advanced tools
Comparing version 1.9.1 to 1.9.2
{ | ||
"name": "ios-deploy", | ||
"version": "1.9.1", | ||
"version": "1.9.2", | ||
"os": [ | ||
@@ -5,0 +5,0 @@ "darwin" |
@@ -77,2 +77,3 @@ [![Build Status](https://travis-ci.org/phonegap/ios-deploy.svg?branch=master)](https://travis-ci.org/phonegap/ios-deploy) | ||
-n, --nostart do not start the app when debugging | ||
-N, --nolldb start debugserver only. do not run lldb | ||
-I, --noninteractive start in non interactive mode (quit when app crashes or exits) | ||
@@ -96,2 +97,3 @@ -L, --justlaunch just launch the app and exit lldb | ||
-W, --no-wifi ignore wifi devices | ||
--detect_deadlocks <sec> start printing backtraces for all threads periodically after specific amount of seconds | ||
@@ -114,2 +116,5 @@ ## Examples | ||
// Debug your pre-installed app with an external debugger (e.g. lldb or IDA Pro) | ||
ios-deploy --noinstall --nolldb --port 6666 --bundle my.app | ||
// Upload a file to your app's Documents folder | ||
@@ -148,1 +153,4 @@ ios-deploy --bundle_id 'bundle.id' --upload test.txt --to Documents/test.txt | ||
* `make debug` will install demo.app and launch a LLDB session. | ||
## Notes | ||
* `--detect_deadlocks` can help to identify an exact state of application's threads in case of a deadlock. It works like this: The user specifies the amount of time ios-deploy runs the app as usual. When the timeout is elapsed ios-deploy starts to print call-stacks of all threads every 5 seconds and the app keeps running. Comparing threads' call-stacks between each other helps to identify the threads which were stuck. |
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
178737
159
153