value_copy: Assertion `arg->contents != nullptr' failed.

[Balika011]

When debugging RP2040 with vscode this assert makes gdb crash.
This is a new assert, that wasn't present in gdb 11.
The fix is easy, replace `if (!value_lazy (val))` to `if (!value_lazy (val) && arg->contents != nullptr) `.

[Andrea (mariofutire86)]

Got the same issue in VSCode using gdb 12.0.90.

I compiled gdb 12.1 and it works.
Can we get it updated to 12.1?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[jamie pate (jamie-pate)]

see also https://sourceware.org/bugzilla/show_bug.cgi?id=29045#c3 where the gdb list recommends updating to a stable version of gdb

[Hoernchen (hoernchen)]

It would be much appreciated if a LTS version of ubuntu would not ship completely broken random master branch checkouts for months.

See also https://github.com/microsoft/vscode-cpptools/issues/9135

[enygmata (heuripedes)]

This was fixed by upstream in april. See https://sourceware.org/bugzilla/show_bug.cgi?id=28980

[Kevin Puetz (puetzk)]

And there's a build for kinetic that contains the fix, which does actually install and work on jammy (since no other dependencies changed too much, at least not yet): https://github.com/microsoft/vscode-cpptools/issues/103#issuecomment-1151217772

[michael (reeves-87)]

Please don't push arbitrary unstable builds into your "stable" update stream as if they were normal updates. I will no longer use your defective gdb packaging given this information.

[Michael Hudson-Doyle (mwhudson)]

https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1971474 tracks the update of gdb to the 12.1 final release. You could try installing gdb from jammy-proposed and see if that helps?