- This topic has 1 reply, 2 voices, and was last updated 1 year, 9 months ago by
.
-
Posts
-
setup visualGDB to debug yocto project through VM.
Visualstudio+visualGDB -> Linux yocto toolchain -> target host
VisualGDB session exit prematurely
Thank you for your purchase. Your license details will be loaded and shown in the next 24-48 hours.
/opt/poky/3.3.5/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/x86_64-poky-linux-gdb –interpreter mi –args “/home/jeffrey/DRXBranch_G4/drx-build/DRXApp/DRXApp”
sh: 1: source: not found
Warning: could not set a breakpoint on main. ‘Step into new instance’ will not work.Exception details:
VisualGDB version: 5.6.109.4777
—————— dn2+b ——————
dn2+b: GDB session exited prematurely. Please verify that the project is built, the selected GDB binary exists and the working directory is specified correctly. If GDB reports an internal error, try updating GDB or erasing the target’s FLASH memory using external tools.
at dn2.z1()
at d12.y_4()
at VisualGDB.GDBDebugEngine.g1(q03 b, h1 a)
trace=[dn2.z1:10071, d12.y_4:22, VisualGDB.GDBDebugEngine.g1:58]Hi,
Thanks for renewing your license.
This error happens because VisualGDB tries to use the shell executable on the target in order to pass some additional environment variables to gdb. The executable is likely broken, or named in an unexpected way, and this triggers the problem.
You can find out the exact command line used by VisualGDB via View->Other Windows->VisualGDB Diagnostics Console (you need to enable it, then reproduce the problem, then check the output for the full command line mentioning the gdb executable).
Once you find out the command line, please try running it manually via an SSH client, and ensure that you get the same error message. If you could share the exact command line you extracted, and more details about your system (e.g. the correct path of the tool referenced in the command line), we can help you configure VisualGDB to adjust it accordingly.
- You must be logged in to reply to this topic.