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 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
