gdb crashes when run from VSCode

[Lowell Boggs]

I had no pre-existing breakpoints in VSCode, then added a breakpoint, and used F5 to run the debugger to the one breakpoint. It crashed before it got there. This is a C++ executable compiled for debugging using CMAKE. I can successfully debug the program using the TUI mode of gdb, so I think the problem likes in the vscode interface to gdb.

/build/gdb-wIRHdd/gdb-12.0.90/gdb/value.c:1731: internal-error: value_copy: Assertion `arg->contents != nullptr' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) [answered Y; input not from terminal]
/build/gdb-wIRHdd/gdb-12.0.90/gdb/value.c:1731: internal-error: value_copy: Assertion `arg->contents != nullptr' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) [answered Y; input not from terminal]

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gdb 12.0.90-0ubuntu1
ProcVersionSignature: Ubuntu 5.14.0-1051.58-oem 5.14.21
Uname: Linux 5.14.0-1051-oem x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 24 11:10:11 2022
InstallationDate: Installed on 2022-02-15 (221 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: gdb
UpgradeStatus: Upgraded to jammy on 2022-09-06 (18 days ago)

[Michael Hudson-Doyle (mwhudson)]

Could you try the gdb from proposed? I think it should help.

[Lowell Boggs (lboggsamida)]

I think I found it, never mind!

Hi Michael,

Thanks for your help! I have never dealt with this bug system before. Where can I find the details of the "proposed" that you mentioned?

Thanks again,
Lowell

[Lowell Boggs (lboggsamida)]

I attempted to install this:
   git clone -b applied/ubuntu/jammy-proposed https://git.launchpad.net/ubuntu/+source/gdb

I then downloaded and cd'd into gdb and ran

   ./configure
   make

but got this error:

checking for iconv declaration...
         extern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft, char * *outbuf, size_t *outbytesleft);
checking for library containing waddstr... -lncursesw
checking for library containing tgetent... none required
checking size of unsigned long long... 8
checking size of unsigned long... 8
checking size of unsigned __int128... 16
checking for library containing dlopen... none required
checking whether to use expat... auto
checking for libexpat... yes
checking how to link with libexpat... -lexpat
checking for XML_StopParser... yes
checking for libgmp... no
configure: error: GMP is missing or unusable
make[1]: *** [Makefile:12137: configure-gdb] Error 1
make[1]: Leaving directory '/home/amida/gdb/gdb'
make: *** [Makefile:1001: all] Error 2

Then I tried to install GMP like this, but it failed

make: *** [Makefile:1001: all] Error 2
gdb: sudo apt-get install GMP
[sudo] password for amida:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package GMP
gdb:

Should I try using the lboggsAmida link instead? I'll try it.

[Lowell Boggs (lboggsamida)]

Ok, the jammy-proposed link did not work for me -- apparently I am not set up as a developer.

I'm running on the latest ubuntu (20.10.04.1) on a thinkpad.

So I tried installing package libgmp-dev and that installed ok. However, when I tried running "make" in the gdb directory, I got a different error this time -- earlier actually.

make[3]: Circular doc/bfd.stamp <- doc/bfd.texi dependency dropped.
  CCLD doc/chew.stamp
  GEN doc/aoutx.stamp
  GEN doc/archive.stamp
  GEN doc/archures.stamp
  GEN doc/bfdio.stamp
  GEN doc/bfdt.stamp
  GEN doc/bfdwin.stamp
  GEN doc/cache.stamp
  GEN doc/coffcode.stamp
  GEN doc/corefile.stamp
  GEN doc/elfcode.stamp
  GEN doc/elf.stamp
  GEN doc/format.stamp
  GEN doc/hash.stamp
  GEN doc/init.stamp
  GEN doc/libbfd.stamp
  GEN doc/linker.stamp
  GEN doc/mmo.stamp
  GEN doc/opncls.stamp
  GEN doc/reloc.stamp
  GEN doc/section.stamp
  GEN doc/syms.stamp
  GEN doc/targets.stamp
  MAKEINFO doc/bfd.info
/home/amida/gdb/gdb/missing: 81: makeinfo: not found
WARNING: 'makeinfo' is missing on your system.
         You should only need it if you modified a '.texi' file, or
         any other file indirectly affecting the aspect of the manual.
         You might want to install the Texinfo package:
         <http://www.gnu.org/software/texinfo/>
         The spurious makeinfo call might also be the consequence of
         using a buggy 'make' (AIX, DU, IRIX), in which case you might
         want to install GNU make:
         <http://www.gnu.org/software/make/>
make[3]: *** [Makefile:1789: doc/bfd.info] Error 127

so I tried rm -f on the gdb directory, then re-cloned it using the https link from jammy-proposed , then did ./configure and make but got the same error.

Sorry for the annoyance

[Lowell Boggs (lboggsamida)]

The above error seemed to be some kind of documentation problem, so I tried just running
   make -k
To ignore errors and everything else make ok. However, I am not able to figure out where the gdb executable is so that I can test it before running "make install".

Here are the places that I found non-script executables:

gdb: find . -executable -type f | grep -v '\.sh$\|\.py$' | xargs file | grep -v ASCII
./readline/readline/doc/texi2html: Perl script text executable
./.git/hooks/fsmonitor-watchman.sample: Perl script text executable
./gnulib/import/extra/update-copyright: POSIX shell script, Unicode text, UTF-8 text executable
./bfd/mep-relocs.pl: Perl script text executable
./bfd/doc/chew: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=a7f2e26778189b6fa5a8675c2d3ea9db3fd7b168, for GNU/Linux 3.2.0, with debug_info, not stripped
./gdbserver/gdbreplay: ELF 64-bit LSB pie executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=cf4af0280f74cd3ea9e88c80aaf267f0f208d822, for GNU/Linux 3.2.0, with debug_info, not stripped
./gdbserver/libinproctrace.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=59bf85a1f1ffb7172042b876671dc397796cde34, with debug_info, not stripped
./gdbserver/gdbserver: ELF 64-bit LSB pie executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=4e460b6a03d64eb6b35e5177be38e519831ca0c8, for GNU/Linux 3.2.0, with debug_info, not stripped
gdb:

Is one of these the gdb executable so I can test it? Thanks

[Michael Hudson-Doyle (mwhudson)]

Oh yikes I'm sorry for giving you incomplete advice. These are the instructions to follow: https://wiki.ubuntu.com/Testing/EnableProposed -- no building from source required!

[Lowell Boggs (lboggsamida)]

I have tried this but am not making much progress.

I was able to run the Software and Updates program and use the Developer Options menu to select the
pre-released updates (jammy-proposed). I then exited the updater and came back in to confirm that the red check mark was there and it was.

However, when I went to the next step, the "updates" page looks nothing like the example documentation that you gave me. Instead, I see the file attached in updater-updates-menu.png

I did try changing the "subscribed to" from "custom" to "all updates". However, when I pressed the close button at the bottom, the Sofware and Updates menu vanished from the screen as if it had crashed. When I restarted it, I could that my selection of back to "custom", and further, the red checkmark for the pre-released (jammy-proposed) was turned off.

Each time I changed one of these two fields, it crashed the updater and turned off the settings I had just made.

Is there a log I can send you that would be helpful?

Thanks,

[Lowell Boggs (lboggsamida)]

Should I report this issue with Software and Updater not keeping the pre-released check after I try to change the Update menu to select all changes?

[Dave Jones (waveform)]

It would probably be best to report the crash in the "Software and Updates" tool separately against the software-properties package (https://launchpad.net/ubuntu/+source/software-properties).

In the meantime you'll want to select "Pre-released Updates" on the "Developer Options" tab at the end of the window, rather than the "Updates" tab as shown in your screenshot.

[Lowell Boggs (lboggsamida)]

Thanks!

--
Lowell Boggs
Senior Software Engineer
Amida Technology Solutions, Inc.
m: 214-789-8560

On Thu, Sep 29, 2022 at 3:55 PM Dave Jones <email address hidden>
wrote:

> It would probably be best to report the crash in the "Software and
> Updates" tool separately against the software-properties package
> (https://launchpad.net/ubuntu/+source/software-properties).
>
> In the meantime you'll want to select "Pre-released Updates" on the
> "Developer Options" tab at the end of the window, rather than the
> "Updates" tab as shown in your screenshot.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1990729
>
> Title:
> gdb crashes when run from VSCode
>
> Status in gdb package in Ubuntu:
> New
>
> Bug description:
> I had no pre-existing breakpoints in VSCode, then added a breakpoint,
> and used F5 to run the debugger to the one breakpoint. It crashed
> before it got there. This is a C++ executable compiled for debugging
> using CMAKE. I can successfully debug the program using the TUI mode
> of gdb, so I think the problem likes in the vscode interface to gdb.
>
> /build/gdb-wIRHdd/gdb-12.0.90/gdb/value.c:1731: internal-error:
> value_copy: Assertion `arg->contents != nullptr' failed.
> A problem internal to GDB has been detected,
> further debugging may prove unreliable.
> Quit this debugging session? (y or n) [answered Y; input not from
> terminal]
> /build/gdb-wIRHdd/gdb-12.0.90/gdb/value.c:1731: internal-error:
> value_copy: Assertion `arg->contents != nullptr' failed.
> A problem internal to GDB has been detected,
> further debugging may prove unreliable.
> Create a core file of GDB? (y or n) [answered Y; input not from terminal]
>
> ProblemType: Bug
> DistroRelease: Ubuntu 22.04
> Package: gdb 12.0.90-0ubuntu1
> ProcVersionSignature: Ubuntu 5.14.0-1051.58-oem 5.14.21
> Uname: Linux 5.14.0-1051-oem x86_64
> NonfreeKernelModules: nvidia_modeset nvidia
> ApportVersion: 2.20.11-0ubuntu82.1
> Architecture: amd64
> CasperMD5CheckResult: unknown
> CurrentDesktop: ubuntu:GNOME
> Date: Sat Sep 24 11:10:11 2022
> InstallationDate: Installed on 2022-02-15 (221 days ago)
> InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64
> (20200731)
> RebootRequiredPkgs: Error: path contained symlinks.
> SourcePackage: gdb
> UpgradeStatus: Upgraded to jammy on 2022-09-06 (18 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1990729/+subscriptions
>
>

[Lowell Boggs (lboggsamida)]

thanks, I set the pre-release items on the software updater, and triggered
an update. But I saw nothing about gdb in the things it was going to
update.
Without me telling it to update all packages in the "Updates" menu of
software and updates, how do I make it update the gdb?
Thanks

--
Lowell Boggs
Senior Software Engineer
Amida Technology Solutions, Inc.
m: 214-789-8560

On Thu, Sep 29, 2022 at 3:55 PM Dave Jones <email address hidden>
wrote:

> It would probably be best to report the crash in the "Software and
> Updates" tool separately against the software-properties package
> (https://launchpad.net/ubuntu/+source/software-properties).
>
> In the meantime you'll want to select "Pre-released Updates" on the
> "Developer Options" tab at the end of the window, rather than the
> "Updates" tab as shown in your screenshot.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1990729
>
> Title:
> gdb crashes when run from VSCode
>
> Status in gdb package in Ubuntu:
> New
>
> Bug description:
> I had no pre-existing breakpoints in VSCode, then added a breakpoint,
> and used F5 to run the debugger to the one breakpoint. It crashed
> before it got there. This is a C++ executable compiled for debugging
> using CMAKE. I can successfully debug the program using the TUI mode
> of gdb, so I think the problem likes in the vscode interface to gdb.
>
> /build/gdb-wIRHdd/gdb-12.0.90/gdb/value.c:1731: internal-error:
> value_copy: Assertion `arg->contents != nullptr' failed.
> A problem internal to GDB has been detected,
> further debugging may prove unreliable.
> Quit this debugging session? (y or n) [answered Y; input not from
> terminal]
> /build/gdb-wIRHdd/gdb-12.0.90/gdb/value.c:1731: internal-error:
> value_copy: Assertion `arg->contents != nullptr' failed.
> A problem internal to GDB has been detected,
> further debugging may prove unreliable.
> Create a core file of GDB? (y or n) [answered Y; input not from terminal]
>
> ProblemType: Bug
> DistroRelease: Ubuntu 22.04
> Package: gdb 12.0.90-0ubuntu1
> ProcVersionSignature: Ubuntu 5.14.0-1051.58-oem 5.14.21
> Uname: Linux 5.14.0-1051-oem x86_64
> NonfreeKernelModules: nvidia_modeset nvidia
> ApportVersion: 2.20.11-0ubuntu82.1
> Architecture: amd64
> CasperMD5CheckResult: unknown
> CurrentDesktop: ubuntu:GNOME
> Date: Sat Sep 24 11:10:11 2022
> InstallationDate: Installed on 2022-02-15 (221 days ago)
> InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64
> (20200731)
> RebootRequiredPkgs: Error: path contained symlinks.
> SourcePackage: gdb
> UpgradeStatus: Upgraded to jammy on 2022-09-06 (18 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1990729/+subscriptions
>
>

[Lowell Boggs (lboggsamida)]

The update that I just made does seem to have fixed the problem that I was
having with GDB when used under VS Code.

Thanks very much for the help!

--
Lowell Boggs
Senior Software Engineer
Amida Technology Solutions, Inc.
m: 214-789-8560

On Thu, Sep 29, 2022 at 5:37 PM Lowell Boggs <email address hidden> wrote:

> thanks, I set the pre-release items on the software updater, and triggered
> an update. But I saw nothing about gdb in the things it was going to
> update.
> Without me telling it to update all packages in the "Updates" menu of
> software and updates, how do I make it update the gdb?
> Thanks
>
> --
> Lowell Boggs
> Senior Software Engineer
> Amida Technology Solutions, Inc.
> m: 214-789-8560
>
>
> On Thu, Sep 29, 2022 at 3:55 PM Dave Jones <email address hidden>
> wrote:
>
>> It would probably be best to report the crash in the "Software and
>> Updates" tool separately against the software-properties package
>> (https://launchpad.net/ubuntu/+source/software-properties).
>>
>> In the meantime you'll want to select "Pre-released Updates" on the
>> "Developer Options" tab at the end of the window, rather than the
>> "Updates" tab as shown in your screenshot.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1990729
>>
>> Title:
>> gdb crashes when run from VSCode
>>
>> Status in gdb package in Ubuntu:
>> New
>>
>> Bug description:
>> I had no pre-existing breakpoints in VSCode, then added a breakpoint,
>> and used F5 to run the debugger to the one breakpoint. It crashed
>> before it got there. This is a C++ executable compiled for debugging
>> using CMAKE. I can successfully debug the program using the TUI mode
>> of gdb, so I think the problem likes in the vscode interface to gdb.
>>
>> /build/gdb-wIRHdd/gdb-12.0.90/gdb/value.c:1731: internal-error:
>> value_copy: Assertion `arg->contents != nullptr' failed.
>> A problem internal to GDB has been detected,
>> further debugging may prove unreliable.
>> Quit this debugging session? (y or n) [answered Y; input not from
>> terminal]
>> /build/gdb-wIRHdd/gdb-12.0.90/gdb/value.c:1731: internal-error:
>> value_copy: Assertion `arg->contents != nullptr' failed.
>> A problem internal to GDB has been detected,
>> further debugging may prove unreliable.
>> Create a core file of GDB? (y or n) [answered Y; input not from
>> terminal]
>>
>> ProblemType: Bug
>> DistroRelease: Ubuntu 22.04
>> Package: gdb 12.0.90-0ubuntu1
>> ProcVersionSignature: Ubuntu 5.14.0-1051.58-oem 5.14.21
>> Uname: Linux 5.14.0-1051-oem x86_64
>> NonfreeKernelModules: nvidia_modeset nvidia
>> ApportVersion: 2.20.11-0ubuntu82.1
>> Architecture: amd64
>> CasperMD5CheckResult: unknown
>> CurrentDesktop: ubuntu:GNOME
>> Date: Sat Sep 24 11:10:11 2022
>> InstallationDate: Installed on 2022-02-15 (221 days ago)
>> InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64
>> (20200731)
>> RebootRequiredPkgs: Error: path contained symlinks.
>> SourcePackage: gdb
>> UpgradeStatus: Upgraded to jammy on 2022-09-06 (18 days ago)
>>
>> To manage notifications about this bug go to...

[Lowell Boggs (lboggsamida)]

I just retested after updating using the pre-release sw setting.

the problem has been fixed.

thank you for your assistance. Please close the ticket as "fixed".

[Nick Rosbrook (enr0n)]

Lowell - Thank you for testing and confirming that the gdb SRU[1] fixes this!

[1] https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1971474