Debugging JavaScript on Native Platforms

    If a game can only run on a physical device, then the packaged game must be debugged on a physical device. Debugging steps are as follows:

    • Select the Android/iOS platform and Debug mode in the Build panel to build, compile and run a project (for the iOS platform, it is recommended to connect to the physical device via Xcode to compile and run).

    • Open this address with Chrome browser: devtools://devtools/bundled/js_app.html?v8only=true&ws=Local IP of the device:6086/00010002-0003-4004-8005-000600070008.

    The steps for debugging a game on the Windows / Mac platform are similar to the Android / iOS, just compile the project and run it in the IDE.

    • Compile and run the packaged project with the IDE (Visual Studio for Windows and Xcode for Mac).

    • Open Chrome while the game is running and enter the address: to debug it.

      v8-win32-debug

    By using breakpoints in C++, we can easily see the C++ call stack, but not the JS call stack at the same time, which often breaks the debugging experience. The features provided by lldb allow doing a lot of things during debugging, including viewing the call stack.

    lldb will load ~/.lldbinit at startup, for example the following configuration:

    The behavior after setting every breakpoint and executing the following code to output the JS call stack:

    For more information on the usage of target stop-hook, please refer to the Examining Variables documentation.

    However, this approach has an obvious drawback: it works for all projects and will result in an error if the corresponding symbol does not exist for other projects.

    Editing Action in breakpoints in Xcode (only triggered for specific breakpoints)

    Enter the following command in the Debugger Command:

    Setting stop hook

    After the breakpoint is triggered, a callback needs to be added to the lldb console. More calls can be made for specific breakpoints: the

    xcode-brk-point-lldb

    As above, the call stack can also be viewed by executing the following code:

    Configure in the Run -> Debug Configuration -> Debugger interface of Android Studio:

    Android Studio also provides a similar to Xcode.

    To debug in Release mode, or need to debug a customized native engine, please refer to the more detailed JSB 2.0 Usage Guide: Remote Debugging and Profile documentation.