[Bug 1990729] Re: gdb crashes when run from VSCode

[Lowell Boggs]

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

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gdb in Ubuntu.
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