|
@@ -40,13 +40,13 @@ In certain cases, one might want to add `printf()` statements to the code. After
|
|
|
|
|
|
Note that Defold by default only prints using dmLog* functions in the debug build.
|
|
Note that Defold by default only prints using dmLog* functions in the debug build.
|
|
|
|
|
|
-### [Android](/manuals/extensions-debugging-android.md)
|
|
|
|
|
|
+### [Android](/manuals/extensions-debugging-android)
|
|
|
|
|
|
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.
|
|
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)
|
|
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](/manuals/extensions-debugging-ios.md)
|
|
|
|
|
|
+### [iOS](/manuals/extensions-debugging-ios)
|
|
|
|
|
|
On iOS, you need to open either iTunes or XCode to view the device logs.
|
|
On iOS, you need to open either iTunes or XCode to view the device logs.
|
|
|
|
|