Package: gdb-arm-none-eabi Version: 7.10-1+9 Severity: normal Dear Maintainer,
using the 'run' command on an extended-remote target results in: ../../gdb/gdb/inferior.c:361: internal-error: find_inferior_pid: Assertion `pid != 0' failed. After that, the only available action is terminating the debugging session, optionally creating a core file. As stated here [0], the 'run' command is supported in extended-remote mode, and should work as if the program being debugged was local, and restart it from the beginning when used. A relevant detail may be that it actually works as expected on a different computer i had, which had the very same gdb-arm version from the debian repos (the current one), but on the 32 bit architecture. This is the only difference i can notice between the two. Let me know if additional infos are needed. Thank you. [0] https://sourceware.org/gdb/onlinedocs/gdb/Connecting.html -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.4.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gdb-arm-none-eabi depends on: ii libc6 2.22-6 ii libexpat1 2.1.1-1 ii libncurses5 6.0+20160319-1 ii libpython2.7 2.7.11-7 ii libreadline6 6.3-8+b4 ii libtinfo5 6.0+20160319-1 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages gdb-arm-none-eabi recommends: ii gcc-arm-none-eabi 15:4.9.3+svn231177-1 gdb-arm-none-eabi suggests no packages. -- no debconf information
