[Bug gdb/26861] internal-error: void target_mourn_inferior(ptid_t): Assertion `ptid == inferior_ptid' failed. OS: Mac OSX Catalina; Compiler: GCC; Language: C

["levraiphilippeblain at gmail dot com" <sourceware-bugzilla@sourceware.org>]

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

--- Comment #9 from Philippe Blain <levraiphilippeblain at gmail dot com> ---
Ok so it appears core dumps are not written to the current working directory on
macOS, you learn something new everyday...

So you need to do the following ([1], [2]):

~~~shell
$ ulimit -c unlimited
$ chmod o+w /cores
$ gdb --batch ./test -ex 'b here' -ex run 
# GDB fails as above
$ ls /cores
core.32580
$ lldb -c /cores/core.32580
(lldb) target create --core "/cores/core.32580"
Core file '/cores/core.32580' (x86_64) was loaded.
(lldb) bt
* thread #1: tid = 0x0000, 0x00007fff98713f06
libsystem_kernel.dylib`__pthread_kill + 10, stop reason = signal SIGSTOP
  * frame #0: 0x00007fff98713f06 libsystem_kernel.dylib`__pthread_kill + 10
    frame #1: 0x00007fff94c264ec libsystem_pthread.dylib`pthread_kill + 90
    frame #2: 0x00007fff8a4e36df libsystem_c.dylib`abort + 129
    frame #3: 0x00000001003547cd gdb`internal_vproblem(internal_problem*, char
const*, int, char const*, __va_list_tag*) [inlined] dump_core() + 1325 at
utils.c:204 [opt]
    frame #4: 0x00000001003547a4 gdb`internal_vproblem(problem=<unavailable>,
file=<unavailable>, line=<unavailable>, fmt=<unavailable>, ap=<unavailable>) +
1284 at utils.c:414 [opt]
    frame #5: 0x000000010035427e gdb`internal_verror(file=<unavailable>,
line=<unavailable>, fmt=<unavailable>, ap=<unavailable>) + 30 at utils.c:439
[opt]
    frame #6: 0x0000000100414ad4 gdb`internal_error(file=<unavailable>,
line=<unavailable>, fmt=<unavailable>) + 116 at errors.cc:55 [opt]
    frame #7: 0x00000001003035ac gdb`target_mourn_inferior(ptid=<unavailable>)
+ 124 at target.c:2149 [opt]
    frame #8: 0x00000001000df487
gdb`darwin_nat_target::kill(this=<unavailable>) + 791 at darwin-nat.c:1535
[opt]
    frame #9: 0x000000010032796f gdb`quit_force(int*, int) [inlined]
kill_or_detach(inf=<unavailable>, from_tty=<unavailable>) + 207 at top.c:1689
[opt]
    frame #10: 0x0000000100327921 gdb`quit_force(exit_arg=<unavailable>,
from_tty=<unavailable>) + 129 at top.c:1780 [opt]
    frame #11: 0x00000001001f06a8 gdb`captured_main_1(context=<unavailable>) +
9592 at main.c:1234 [opt]
    frame #12: 0x00000001001ee06f gdb`gdb_main(captured_main_args*) [inlined]
captured_main(void*) + 11 at main.c:1243 [opt]
    frame #13: 0x00000001001ee064 gdb`gdb_main(args=<unavailable>) + 4 at
main.c:1268 [opt]
    frame #14: 0x0000000100000bea gdb`main(argc=<unavailable>,
argv=<unavailable>) + 42 at gdb.c:32 [opt]
    frame #15: 0x00007fff8b1495ad libdyld.dylib`start + 1
(lldb) 
~~~

I've never debugged a debugger before, nor done system-level programming so I'm
really at the limit of my knowledge here... I'm willing to help further though.
I'll start by recompiling GDB without optimization.

[1]
https://stackoverflow.com/questions/9412156/how-to-generate-core-dumps-in-mac-os-x
[2]
https://developer.apple.com/library/archive/technotes/tn2124/_index.html#//apple_ref/doc/uid/DTS10003391-CH1-SECCOREDUMPS

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