public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "levraiphilippeblain at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/26861] internal-error: void target_mourn_inferior(ptid_t): Assertion `ptid == inferior_ptid' failed. OS: Mac OSX Catalina; Compiler: GCC; Language: C Date: Tue, 23 Feb 2021 03:27:38 +0000 [thread overview] Message-ID: <bug-26861-4717-rdYIxE70b6@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26861-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26861 Philippe Blain <levraiphilippeblain at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |levraiphilippeblain at gmail dot c | |om --- Comment #8 from Philippe Blain <levraiphilippeblain at gmail dot com> --- I also get this error on my old macOS 10.11.6 system with a self-compiled GDB 10.1. This did not happen with GDB 8.3.1 which I was using previously. So it is definitely not specific to ARM or even Big Sur... My reproducer program: ~~~cpp # test.cpp void here() {}; int main() { const int size = 5; double array[size] = {1.0, 2.0, 3.0, 4.0, 5.0}; here(); return 0; } ~~~ I build that example and invoke GDB like so: ~~~shell $ g++ --version Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1 Apple LLVM version 8.0.0 (clang-800.0.42.1) Target: x86_64-apple-darwin15.6.0 Thread model: posix InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin $ g++ -O0 -g test.cpp -o test $ gdb --configuration This GDB was configured as follows: configure --host=x86_64-apple-darwin15.6.0 --target=x86_64-apple-darwin15.6.0 --with-auto-load-dir=:${prefix}/share/auto-load --with-auto-load-safe-path=:${prefix}/share/auto-load --with-expat --with-gdb-datadir=/usr/local/Cellar/gdb/10.1/share/gdb (relocatable) --with-jit-reader-dir=/usr/local/Cellar/gdb/10.1/lib/gdb (relocatable) --without-libunwind-ia64 --without-lzma --without-babeltrace --without-intel-pt --with-mpfr --without-xxhash --with-python=/usr/local/Cellar/python/3.7.7/Frameworks/Python.framework/Versions/3.7 --with-python-libdir=/usr/local/Cellar/python/3.7.7/Frameworks/Python.framework/Versions/3.7/lib --without-debuginfod --without-guile --disable-source-highlight --with-separate-debug-dir=/usr/local/Cellar/gdb/10.1/lib/debug (relocatable) ("Relocatable" means the directory can be moved with the GDB installation tree, and GDB will still find it.) $ gdb --batch ./test -ex 'b here' -ex run Breakpoint 1 at 0x100000e74: file test.cpp, line 1. [New Thread 0x1403 of process 30980] Breakpoint 1, here () at test.cpp:1 1 void here() {}; warning: Mach error at "../../gdb-10.1/gdb/darwin-nat.c:453" in function "void darwin_resume_inferior(struct inferior *)": (ipc/send) invalid destination port (0x10000003) ../../gdb-10.1/gdb/target.c:2149: internal-error: void target_mourn_inferior(ptid_t): Assertion `ptid == inferior_ptid' 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] This is a bug, please report it. For instructions, see: <https://www.gnu.org/software/gdb/bugs/>. ../../gdb-10.1/gdb/target.c:2149: internal-error: void target_mourn_inferior(ptid_t): Assertion `ptid == inferior_ptid' 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] Abort trap: 6 ~~~ Note that no core file is generated despite the last message... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-02-23 3:27 UTC|newest] Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-10 9:46 [Bug gdb/26861] New: " ntvallone at ucdavis dot edu 2020-11-10 9:47 ` [Bug gdb/26861] " ntvallone at ucdavis dot edu 2020-11-29 19:25 ` ethanrob122 at gmail dot com 2020-11-29 19:37 ` ethanrob122 at gmail dot com 2021-01-20 1:15 ` fishinfuglers at gmail dot com 2021-01-31 7:42 ` frankshe175 at gmail dot com 2021-02-01 19:07 ` simark at simark dot ca 2021-02-01 19:10 ` simark at simark dot ca 2021-02-10 15:05 ` rostyslav.skrypnyk at gmail dot com 2021-02-23 3:27 ` levraiphilippeblain at gmail dot com [this message] 2021-02-23 3:53 ` levraiphilippeblain at gmail dot com 2021-02-24 4:19 ` levraiphilippeblain at gmail dot com 2021-02-24 16:41 ` simark at simark dot ca 2021-02-24 17:11 ` simark at simark dot ca 2021-02-24 20:07 ` levraiphilippeblain at gmail dot com 2021-02-24 20:16 ` levraiphilippeblain at gmail dot com 2021-02-24 22:04 ` simark at simark dot ca 2021-02-25 20:53 ` cvs-commit at gcc dot gnu.org 2021-02-25 20:55 ` cvs-commit at gcc dot gnu.org 2021-02-25 20:57 ` simark at simark dot ca 2021-02-28 11:41 ` brobecker at gnat dot com 2021-06-27 17:47 ` ahmedsayeed1982 at yahoo dot com 2021-08-18 13:52 ` jamesrogan59 at gmail dot com 2021-08-25 5:16 ` marlenesanchez231+wilmar at gmail dot com 2021-09-02 11:03 ` donipah907 at mtlcz dot com 2021-09-02 11:05 ` donipah907 at mtlcz dot com 2021-09-02 11:17 ` mark at klomp dot org 2021-09-05 7:36 ` kimolsun2020 at yahoo dot com 2021-09-06 9:06 ` focixujo at livinginsurance dot co.uk 2021-09-06 9:12 ` focixujo at livinginsurance dot co.uk 2021-09-06 13:09 ` ntvallone at ucdavis dot edu 2021-09-10 19:37 ` mehmetgelisin at aol dot com 2021-09-13 8:40 ` nicholasgrove641 at gmail dot com 2021-09-13 8:41 ` nicholasgrove641 at gmail dot com 2021-09-13 8:41 ` nicholasgrove641 at gmail dot com 2021-09-13 8:41 ` nicholasgrove641 at gmail dot com 2021-09-28 1:40 ` marlenesanchez231+jaime at gmail dot com 2021-10-08 19:40 ` vficaj at gmail dot com 2021-10-09 11:00 ` gulsenenginar at aol dot com 2021-10-18 19:58 ` ahmedsayeed1982 at hotmail dot com 2021-10-19 7:14 ` progonsaytu at gmail dot com 2021-10-24 10:02 ` glassmtech at ukr dot net 2021-11-10 1:57 ` wallremovalsperth at gmail dot com 2021-11-10 1:59 ` wallremovalsperth at gmail dot com 2021-11-22 6:48 ` gexed96894 at keagenan 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-26861-4717-rdYIxE70b6@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).