public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "erickitten at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/25560] Assertion `pid != 0' failed Date: Tue, 20 Oct 2020 02:51:57 +0000 [thread overview] Message-ID: <bug-25560-4717-68JDPNoARg@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-25560-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=25560 Che-Kang Wu <erickitten at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |erickitten at gmail dot com --- Comment #9 from Che-Kang Wu <erickitten at gmail dot com> --- I found the same assertion fail on Windows 10 (Mingw32) to ARM cross-gdb when remote debugging. Bug 24825 also shows a similar issue, not sure if this is the same. 1) Example program #include <stdio.h> int main (void) { printf("Hello world!\n"); return 1; } 2) Compile arm-linux-gnueabihf-gcc -g 1.c 3) Remote ./gdbserver :12000 ./a.out Process ./hello created; pid = 1421 Listening on port 12000 4) gdb host arm-linux-gnueabihf-gdb.exe GNU gdb (GDB) 9.2 (gdb) show configuration This GDB was configured as follows: configure --host=i686-w64-mingw32 --target=arm-linux-gnueabihf --with-auto-load-dir=$debugdir:$datadir/auto-load --with-auto-load-safe-path=$debugdir:$datadir/auto-load --with-expat --with-gdb-datadir=/usr/local/share/gdb (relocatable) --with-jit-reader-dir=/usr/local/lib/gdb (relocatable) --without-libunwind-ia64 --without-lzma --without-babeltrace --without-intel-pt --without-mpfr --without-xxhash --without-python --without-guile --disable-source-highlight --with-separate-debug-dir=/usr/local/lib/debug (relocatable) 5) Set breakpoint (gdb) target remote xxx.xxx.xxx.xxx:12000 (gdb) b main (gdb) c Breakpoint 1, main () at 1.c:6 6 printf("Hello world!\n"); 6) This works normally (gdb) c Continuing. [Inferior 1 (process 1463) exited with code 01] (gdb) q 7) But this fails (gdb) n # Next step to end Single stepping until exit from function __libc_start_main, which has no line number information. [Inferior 1 (process 1457) exited with code 01] You can't do that without a process to debug. (gdb) q /home/eric/project/standalone-build/source/gdb-9.2/gdb-build/../gdb/inferior.c:283: internal-error: inferior* find_inferior_pid(int): Assertion `pid != 0' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) y -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-10-20 2:51 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-25560-4717@http.sourceware.org/bugzilla/> 2020-08-02 15:43 ` delta512.dev at protonmail dot com 2020-08-02 15:46 ` delta512.dev at protonmail dot com 2020-08-02 15:48 ` delta512.dev at protonmail dot com 2020-08-02 15:51 ` delta512.dev at protonmail dot com 2020-08-09 20:33 ` tromey at sourceware dot org 2020-08-10 21:05 ` delta512.dev at protonmail dot com 2020-08-10 21:08 ` delta512.dev at protonmail dot com 2020-08-10 21:14 ` delta512.dev at protonmail dot com 2020-10-20 2:51 ` erickitten at gmail dot com [this message] 2020-12-13 13:15 ` ddresser at bmc dot com 2021-06-25 19:00 ` dahllunde at gmail dot com 2021-06-25 20:56 ` delta512.dev at protonmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-25560-4717-68JDPNoARg@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).