Review fixes

docs/en/manuals/extensions-debugging-android.md

@@ -36,7 +36,7 @@ Here we list some ways to debug your executable running on an Android Device
 
 	![path_mapping2](images/extensions/debugging/android/path_mappings_android2.png)
 
-* If you have access to the engine source, ad a path mapping to that too
+* If you have access to the engine source, add a path mapping to that too
 
 		* make sure to checkout the version you are currently debugging
 
@@ -69,5 +69,10 @@ is random for each build, making the path mapping invalid for each build.
 However, it works fine for a debugging session.
 
 The path mappings are stored in the <project>.iml file in the Android Studio project.
-It's possible to get the job folder from
+
+It's possible to get the job folder from the executable
+
+	$ arm-linux-androideabi-readelf --string-dump=.debug_str build/armv7-android/libdmengine.so | grep /job
+
+The jobfolder is named like so `job1298751322870374150`, each time with a random number.
 

docs/en/manuals/extensions-debugging-ios.md

@@ -4,15 +4,15 @@ Here we describe how to debug a build using [XCode](https://developer.apple.com/
 
 ## Xcode
 
-* Bundle the app as using bob, with the `--with-symbols` option
+* Bundle the app by using bob, with the `--with-symbols` option
 
 		$ cd myproject
 		$ wget http://d.defold.com/archive/<sha1>/bob/bob.jar
-		$ java -jar bob.jar --platform armv7-darwin build --with-symbols debug --archive bundle -bo build/ios -mp <app>.mobileprovision --identity "iPhone Developer: Your Name (ID)" -bo build/ios
+		$ java -jar bob.jar --platform armv7-darwin build --with-symbols debug --archive bundle -bo build/ios -mp <app>.mobileprovision --identity "iPhone Developer: Your Name (ID)"
 
 * Install the app, either with `XCode`, `iTunes` or [ios-deploy](https://github.com/ios-control/ios-deploy)
 
-		$ ios-deploy -b VideoPlayer.ipa
+		$ ios-deploy -b <AppName>.ipa
 
 * Get the `.dSYM` folder (i.e the debug symbols)
 
@@ -102,6 +102,11 @@ You have a few options to debug an app
 		(lldb) settings set target.source-map /Users/builder/ci/builds/engine-ios-64-master/build /Users/mathiaswesterdahl/work/defold
 		(lldb) settings append target.source-map /private/var/folders/m5/bcw7ykhd6vq9lwjzq1mkp8j00000gn/T/job4836347589046353012/upload/videoplayer/src /Users/mathiaswesterdahl/work/projects/extension-videoplayer-native/videoplayer/src
 
+	* It's possible to get the job folder from the executable.
+	The jobfolder is named like so `job1298751322870374150`, each time with a random number.
+
+			$ dsymutil -dump-debug-map <executable> 2>&1 >/dev/null | grep /job
+
 * Verify the source mappings
 
 		(lldb) settings show target.source-map
@@ -110,6 +115,7 @@ You can check what source file a symbol was originating from using
 
 	(lldb) image lookup -va <SymbolName>
 
+
 ### Breakpoints
 
 * Open a file in the project view, and set a breakpoint

docs/en/manuals/extensions-debugging.md

@@ -25,6 +25,7 @@ And each tool can debug certain platforms:
 * Visual studio - Windows + platforms supporting gdbserver (E.g. Linux/Android)
 * VSCode - Windows, macOS (lldb), Linux (lldb/gdb) + platforms supporting gdbserver
 * XCode -  macOS, iOS
+* Android Studio - Android
 * WinDBG - Windows
 * lldb/gdb - macOS, Linux, (iOS)
 * ios-deploy - iOS (via lldb)
@@ -33,18 +34,18 @@ And each tool can debug certain platforms:
 ## Print debugging
 
 In certain cases, one might want to add printf() statements to the code.
-Afterwards, you can get the logs from your device ana analyze them.
+Afterwards, you can get the logs from your device and analyze them.
 
 Note that Defold by default only prints using dmLog* functions in the debug build.
 
-### Android
+### [Android](./extensions-debugging-android.md)
 
 On Android, the simplest way to get the log is to run `adb` in the terminal.
 You can also see the `console` inside Android Studio, which is the same thing.
 
 If you get hold of a stack trace from the Android logs, you might be able to symbolicate it using [ndk-stack](https://developer.android.com/ndk/guides/ndk-stack.html)
 
-### iOS
+### [iOS](./extensions-debugging-ios.md)
 
 On iOS, you need to open either iTunes or XCode to view the device logs.
 
@@ -69,12 +70,11 @@ If the app is [debuggable](https://www.defold.com/manuals/project-settings/#_and
 
 #### iOS
 
-In iTunes, you can vie/download an apps container.
+In iTunes, you can view/download an apps container.
 
 In the `XCode -> Devices` window, you can also select the crash logs
 
 
-
 ## Symbolication
 
 If you get a callstack from either a `_crash` file or a log file, you can start symbolicate it.