Fix Debugging Issues

​

The app terminates unexpectedly during debugging, interrupting the session

1. From the device’s shell, run:
   vlcm --help
   
2. Look for the --disable-app-timeout flag in the debug command output.
3. Prevent app termination using one of these options: Option 1: Using Vega Studio (Recommended) a. Open your launch.json file. b. Add or modify the disableAppTimeout setting to true:
   {
    "name": "(script) Launch",
    "type": "kepler",
    "request": "launch",
    "disableAppTimeout": true
   }
   
   c. Save and restart your debugging session. Option 2: Using Vega CLI a. Disable timeouts for your component:
   vlcm debug <component-id> --disable-app-timeout
   
   b. Launch your app:
   kepler device launch-app --appName <component-id>
   
   c. Attach your debugger in Vega Studio.
4. Re-enable timeouts after debugging using one of these options:
   • Vega Studio: Launch the app without the debug configuration
   • Vega CLI: Run then relaunch app
   For information about launching your app, see Run your app.

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "(script) Launch",
            "type": "kepler",
            "request": "launch",
            "keplerMode": "debug",
            "cwd": "${workspaceFolder}",
            "deviceId": "${command:kepler.state.getSelectedDeviceId}",
            "disableAppTimeout": true,
            "perf": {
                "startActivityMonitoring": false
            }
        },
        {
            "name": "(native) Launch",
            "type": "keplerNative",
            "request": "launch",
            "cwd": "${workspaceFolder}",
            "deviceId": "${command:kepler.state.getSelectedDeviceId}",
            "disableAppTimeout": true
        }
    ]
}

​

GDB native debugging error: liblzma.5.dylib not found

{Starting: "/usr/local/bin/gdb" --interpreter=mi
dyld[57162]: Library not loaded: /usr/local/homebrew/opt/xz/lib/liblzma.5.dylibReferenced from: <5BAC9301-8CA6-3EA3-9537-CD0E961C0FAB> /usr/local/bin/gdbReason: tried: '/usr/local/homebrew/opt/xz/lib/liblzma.5.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/homebrew/opt/xz/lib/liblzma.5.dylib' (no such file), '/usr/local/homebrew/opt/xz/lib/liblzma.5.dylib' (no such file)"/usr/local/bin/gdb" exited with code 134 (0x86).ERROR: Unable to start debugging. Unable to establish a connection to GDB. }

1. Install the XZ library:
   brew install xz
   
2. If already installed, try reinstalling:
   brew reinstall xz
   
3. Verify symbolic links:
   brew link xz
   
   If the problem persists, try these additional steps:
4. Clear Homebrew cache:
   brew cleanup
   
5. Update Homebrew:
   brew update && brew upgrade
   

1. Verify that you have the latest version of Homebrew.
2. Some macOS versions might require additional security configurations for GDB.
3. Confirm that you have the necessary permissions to access the library locations.

​

Related topics

• Perform Line-by-Line Debugging with Vega Studio
• Use Chrome DevTools for App Profiling
• Monitor Network Traffic with Charles Proxy