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: Wed, 24 Feb 2021 04:19:47 +0000	[thread overview]
Message-ID: <bug-26861-4717-d7LAp2Ctxi@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26861-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=26861

--- Comment #10 from Philippe Blain <levraiphilippeblain at gmail dot com> ---
I recompiled 10.1 with both CFLAGS and CXXFLAGS set to '-O0 -g' and re-ran my
test. I zippped the core dumped and uploaded it to my dropbox since it's too
big to attach https://www.dropbox.com/s/3jo9fogiuas9cyp/core.52896.zip?dl=1

Here is the backtrace:
~~~
$ lldb -c /cores/core.52896 
(lldb) target create --core "/cores/core.52896"
warning: (x86_64) /cores/core.52896 load command 112 LC_SEGMENT_64 has a
fileoff + filesize (0x257fe000) that extends beyond the end of the file
(0x257fd000), the segment will be truncated to match
Core file '/cores/core.52896' (x86_64) was loaded.
(lldb) bt
* thread #1: tid = 0x0000, 0x00007fffa002bf06
libsystem_kernel.dylib`__pthread_kill + 10, stop reason = signal SIGSTOP
  * frame #0: 0x00007fffa002bf06 libsystem_kernel.dylib`__pthread_kill + 10
    frame #1: 0x00007fff9c53e4ec libsystem_pthread.dylib`pthread_kill + 90
    frame #2: 0x00007fff91dfb6df libsystem_c.dylib`abort + 129
    frame #3: 0x00000001007806d4 gdb`dump_core() + 52 at utils.c:204
    frame #4: 0x0000000100781aba
gdb`internal_vproblem(problem=0x0000000100b8c850,
file="../../gdb-10.1/gdb/target.c", line=2149, fmt="%s: Assertion `%s'
failed.", ap=0x00007fff5fbfd850) + 4746 at utils.c:414
    frame #5: 0x0000000100780815
gdb`internal_verror(file="../../gdb-10.1/gdb/target.c", line=2149, fmt="%s:
Assertion `%s' failed.", ap=0x00007fff5fbfd850) + 53 at utils.c:439
    frame #6: 0x00000001008c5068
gdb`internal_error(file="../../gdb-10.1/gdb/target.c", line=2149, fmt="%s:
Assertion `%s' failed.") + 344 at errors.cc:55
    frame #7: 0x00000001006d216a gdb`target_mourn_inferior(ptid=(m_pid = 52898,
m_lwp = 0, m_tid = 0)) + 90 at target.c:2149
    frame #8: 0x00000001002134d3
gdb`darwin_nat_target::kill(this=0x0000000100ba6260) + 979 at darwin-nat.c:1535
    frame #9: 0x00000001006cb435 gdb`target_kill() + 21 at target.c:300
    frame #10: 0x0000000100701248 gdb`kill_or_detach(inf=0x000000010159c130,
from_tty=0) + 120 at top.c:1689
    frame #11: 0x0000000100700d53 gdb`quit_force(exit_arg=0x0000000000000000,
from_tty=0) + 323 at top.c:1780
    frame #12: 0x000000010046052a
gdb`captured_main_1(context=0x00007fff5fbff6a8) + 19754 at main.c:1234
    frame #13: 0x000000010045b76d gdb`captured_main(data=0x00007fff5fbff6a8) +
29 at main.c:1243
    frame #14: 0x000000010045b6b1 gdb`gdb_main(args=0x00007fff5fbff6a8) + 17 at
main.c:1268
    frame #15: 0x0000000100001083 gdb`main(argc=7, argv=0x00007fff5fbff6f0) +
99 at gdb.c:32
    frame #16: 0x00007fff92a615ad libdyld.dylib`start + 1
~~~

note the "warning" that I was not getting yesterday...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-02-24  4:19 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 [this message]
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-d7LAp2Ctxi@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).