- This topic has 4 replies, 2 voices, and was last updated 30 minutes ago by
.
-
Posts
-
I have been using Visual GDB for ages, I paid for support again yesterday.
Issues I have had:
- Linux project fails on a brand new flashed Raspberry pi. It doesnt understand the results of lsb_release returning trixie
- The linker step never completes on a brand new hello world project, just hangs forever
- Doesnt recognize that gdb server is installed on the raspberry pi, likely a result of #1
I cant even get started on a project.
Output of lsb_release
sualGDB version: 6.0.108.5338
—————— System.Exception ——————
System.Exception: The target system image does not match the selected toolchain:
Command: lsb_release -c
Output:
Codename: trixieat k23.c(zz a)
at k23.a(zz a)
at VisualGDB.Common_GUI.WPF.ItemizedProgressWindow.<>c__DisplayClass2_0`1.<RunAction>b__0()
trace=[k23.c:632, k23.a:71, VisualGDB.Common_GUI.WPF.ItemizedProgressWindow+<>c__DisplayClass2_0`1.<RunAction>b__0:0]ld just grinds forever around 4% of the CPU, using increasingly more memory.
This is on the default hello world project.
Hi,
Sorry for your disappointment. We do not have a toolchain for Trixie yet, hence the warning about lsb_release. You can try downgrading to the Bookworm SD card image (the compatible versions are listed here), building the code directly on Raspberry Pi, or using WSL with the Raspberry Pi’s own toolchain (if they provide one).
We have never encountered ld getting stuck forever on a hello world project. That said, if you ignored the lsb_release warning and resynchronized the toolchain’s sysroot, you would end up with a combination of tools and libraries that was never meant to work together, and that could result in completely unpredictable behavior.
If you are not sure, please try completely deleting the toolchain, and starting from a clean SD card image (make sure it matches the toolchain).
- You must be logged in to reply to this topic.