public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "mehmetgelisin at aol dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tui/26973] gdb crashes when not including the status window in a new layout Date: Fri, 10 Sep 2021 19:36:58 +0000 [thread overview] Message-ID: <bug-26973-4717-RlPierbjvu@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26973-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26973 Mehmet gelisin <mehmetgelisin at aol dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mehmetgelisin at aol dot com --- Comment #9 from Mehmet gelisin <mehmetgelisin at aol dot com> --- It does not happen on every run. My MWE: ``` // test.cpp https://komiya-dental.com/ #include<iostream> int main() { int a{ 4 }; std::cout << "a = " << a << '\n'; return 0; } http://www.iu-bloomington.com/ ``` Simply running the program under GDB yields: ``` (gdb) r Starting program: test-gdb/a.out [New Thread 0x1a03 of process 24826] https://www.webb-dev.co.uk/ [New Thread 0x1b03 of process 24826] warning: unhandled dyld version (17) a = 4 [Inferior 1 (process 24826) exited normally] ``` However, setting breakpoints triggers it: https://waytowhatsnext.com/ ``` (gdb) b main Breakpoint 1 at 0x100003e57: file test.cpp, line 5. (gdb) r Starting program: test-gdb/a.out [New Thread 0x2403 of process 24836] [New Thread 0x2203 of process 24836] http://www.acpirateradio.co.uk/ warning: unhandled dyld version (17) Thread 2 hit Breakpoint 1, main () at test.cpp:5 5 int a{ 4 }; (gdb) r The program being debugged has been started already. Start it from the beginning? (y or n) n http://www.logoarts.co.uk/ Program not restarted. (gdb) q A debugging session is active. Inferior 1 [process 24836] will be killed. Quit anyway? (y or n) y http://www.slipstone.co.uk/ ../../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, http://embermanchester.uk/ further debugging may prove unreliable. Quit this debugging session? (y or n) y This is a bug, please report it. For instructions, see: http://connstr.net/ 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. http://joerg.li/ So it is definitely not specific to ARM or even Big Sur... http://www.jopspeech.com/ My reproducer program: ~~~cpp # test.cpp http://www.wearelondonmade.com/ void here() {}; int main() { const int size = 5; http://www.compilatori.com/ 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: http://www-look-4.com/ ~~~shell $ g++ --version -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-09-10 19:36 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-29 17:40 [Bug tui/26973] New: " ssbssa at sourceware dot org 2020-11-29 17:49 ` [Bug tui/26973] " cvs-commit at gcc dot gnu.org 2020-11-29 17:54 ` cvs-commit at gcc dot gnu.org 2020-11-29 17:55 ` ssbssa at sourceware dot org 2021-06-27 17:48 ` ahmedsayeed1982 at yahoo dot com 2021-09-02 11:06 ` donipah907 at mtlcz dot com 2021-09-02 11:15 ` mark at klomp dot org 2021-09-05 7:36 ` kimolsun2020 at yahoo dot com 2021-09-06 9:08 ` focixujo at livinginsurance dot co.uk 2021-09-06 9:12 ` focixujo at livinginsurance dot co.uk 2021-09-10 19:36 ` mehmetgelisin at aol dot com [this message] 2021-09-14 12:54 ` jarilittlenen at yahoo dot com 2021-09-26 13:31 ` tes.vik1986 at gmail dot com 2021-10-09 11:00 ` gulsenenginar at aol dot com 2021-10-09 16:09 ` studiaviktor at gmail dot com 2021-10-19 7:14 ` progonsaytu at gmail dot com 2021-10-24 10:02 ` glassmtech at ukr dot net 2021-11-13 19:34 ` tesaso8237 at funboxcn 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-26973-4717-RlPierbjvu@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).