public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "gulsenenginar at aol 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: Sat, 09 Oct 2021 11:00:23 +0000 [thread overview]
Message-ID: <bug-26861-4717-O0NXjOwedE@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26861-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26861
Gulsen Engin <gulsenenginar at aol dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gulsenenginar at aol dot com
--- Comment #35 from Gulsen Engin <gulsenenginar at aol dot com> ---
It does not happen on every run. My MWE:
``` http://www-look-4.com/tech/honor-magicbook/
// test.cpp
#include<iostream>
int main() https://komiya-dental.com/property/google-android/
{
int a{ 4 };
std::cout << "a = " << a << '\n';
http://www.iu-bloomington.com/property/properties-in-turkey/
return 0;
}
```
Simply running the program under GDB yields:
``` https://waytowhatsnext.com/property/disney-at-home/
(gdb) r
Starting program: test-gdb/a.out
[New Thread 0x1a03 of process 24826]
[New Thread 0x1b03 of process 24826]
http://www.wearelondonmade.com/technology/van-technology/
warning: unhandled dyld version (17)
a = 4
[Inferior 1 (process 24826) exited normally]
``` http://www.jopspeech.com/technology/thunderbolt-4/
However, setting breakpoints triggers it:
```
(gdb) b main http://joerg.li/technology/b-class-cars/
Breakpoint 1 at 0x100003e57: file test.cpp, line 5.
(gdb) r
Starting program: test-gdb/a.out
[New Thread 0x2403 of process 24836] http://connstr.net/technology/nasa-latest/
[New Thread 0x2203 of process 24836]
warning: unhandled dyld version (17)
http://embermanchester.uk/tech/google-drive/
Thread 2 hit Breakpoint 1, main () at test.cpp:5
5 int a{ 4 };
(gdb) r http://www.slipstone.co.uk/technology/cars-interior/
The program being debugged has been started already.
Start it from the beginning? (y or n) n
Program not restarted. http://www.logoarts.co.uk/technology/robot-vacuums/
(gdb) q
A debugging session is active.
Inferior 1 [process 24836] will be killed.
http://www.acpirateradio.co.uk/technology/global-warming/
Quit anyway? (y or n) y
../../gdb/target.c:2149: internal-error: void target_mourn_inferior(ptid_t):
Assertion `ptid == inferior_ptid' failed.
http://www.compilatori.com/technology/download-videos/
A problem internal to GDB has been detected,
further debugging may prove unreliable.
https://www.webb-dev.co.uk/services/vaccine-services/
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:[~2021-10-09 11:00 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
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 [this message]
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-O0NXjOwedE@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: link
Be 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).