public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "delta512.dev at protonmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25560] Assertion `pid != 0' failed
Date: Mon, 10 Aug 2020 21:05:55 +0000	[thread overview]
Message-ID: <bug-25560-4717-i1K19KOFkK@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25560-4717@http.sourceware.org/bugzilla/>

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

--- Comment #6 from Fil <delta512.dev at protonmail dot com> ---
(In reply to Tom Tromey from comment #5)
> A stack trace of the crashing gdb might be helpful.

Sure, there it is:

#0  0x00000001001bcf50 in find_inferior_pid (pid=<optimized out>) at
../../gdb/inferior.c:283
#1  0x0000000100320aed in find_thread_ptid (ptid=...) at ../../gdb/thread.c:524
#2  inferior_thread () at ../../gdb/thread.c:94
#3  0x000000010028201e in get_thread_arch_regcache (gdbarch=<optimized out>,
ptid=...) at ../../gdb/regcache.c:341
#4  get_thread_regcache (ptid=...) at ../../gdb/regcache.c:358
#5  get_thread_regcache (thread=<optimized out>) at ../../gdb/regcache.c:366
#6  0x0000000102809190 in ?? ()
#7  0x0000000102809190 in ?? ()
#8  0x00007ffeefbff4c0 in ?? ()
#9  0x00000001002bf9a2 in gdb_bfd_ref_policy::decref (abfd=<optimized out>) at
../../gdb/gdb_bfd.h:64
#10 gdb::ref_ptr<bfd, gdb_bfd_ref_policy>::~ref_ptr (this=<optimized out>) at
../../gdb/gdbsupport/gdb_ref_ptr.h:91
#11 gdb::ref_ptr<bfd, gdb_bfd_ref_policy>::~ref_ptr (this=<optimized out>) at
../../gdb/gdbsupport/gdb_ref_ptr.h:89
#12 darwin_get_dyld_bfd () at ../../gdb/solib-darwin.c:446
#13 0x00000001002bed90 in darwin_solib_get_all_image_info_addr_at_init
(info=<optimized out>) at ../../gdb/solib-darwin.c:465
#14 darwin_solib_create_inferior_hook (from_tty=<optimized out>) at
../../gdb/solib-darwin.c:515
#15 0x00000001002dca3f in symbol_file_command (args=<optimized out>,
from_tty=1) at ../../gdb/symfile.c:1674
#16 0x000000010015451d in file_command (arg=0x103026450 "", from_tty=41980304)
at ../../gdb/exec.c:433
#17 0x00000001000963f2 in cmd_func (cmd=0x102809190, args=0x100b232c0 "",
from_tty=0) at ../../gdb/cli/cli-decode.c:1952
#18 0x000000010032876c in execute_command (p=<optimized out>, from_tty=1) at
../../gdb/top.c:612
#19 0x0000000102800f35 in ?? ()
#20 0x0000000100c044c0 in ?? ()
#21 0x00007ffeefbff630 in ?? ()
#22 0x00007fff561fd5bf in malloc () from /usr/lib/system/libsystem_malloc.dylib
#23 0x0000000100151bbb in command_handler (command=0x102809190 "
\214\200\002\001") at ../../gdb/event-top.c:587
#24 0x0000000100151eb0 in command_line_handler (rl=...) at
../../gdb/event-top.c:772
#25 0x0000000100151410 in gdb_rl_callback_handler (rl=0x102809190 "
\214\200\002\001") at ../../gdb/event-top.c:218
#26 0x000000010039a86a in rl_callback_read_char () at
../../../readline/readline/callback.c:281
#27 0x00000001001525fe in gdb_rl_callback_read_char_wrapper_noexcept () at
../../gdb/event-top.c:176
#28 0x00000001001510b4 in gdb_rl_callback_read_char_wrapper
(client_data=<optimized out>) at ../../gdb/event-top.c:193
#29 0x0000000100151a80 in stdin_event_handler (error=<optimized out>,
client_data=0x103026450) at ../../gdb/event-top.c:515
#30 0x0000000100150432 in gdb_wait_for_event (block=<optimized out>) at
../../gdb/event-loop.c:854
#31 0x0000000100150094 in gdb_do_one_event () at ../../gdb/event-loop.c:346
#32 0x0000000100150515 in start_event_loop () at ../../gdb/event-loop.c:370
#33 0x00000001001faa1f in captured_command_loop () at ../../gdb/main.c:359
#34 0x00000001001f7c85 in captured_main (data=<optimized out>) at
../../gdb/main.c:1203
#35 gdb_main (args=<optimized out>) at ../../gdb/main.c:1217
#36 0x0000000100450e60 in ?? ()
#37 0x0000000000000000 in ?? ()

Thanks for your reply, if you need more information please check the new debug
session attached.

> Note that the Darwin port isn't very actively maintained.
> This is unfortunate but we have had trouble finding someone
> with the needed hardware and the desire to make it work :(

Yeah, I guess Apple is of no help anymore too. Unfortunately I'm building GDB
to learn how to use it properly, so my skills are not enough for sure.

Yet, if you could guide me I'll share as much details as possible and hopefully
sort this out.

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

  parent reply	other threads:[~2020-08-10 21:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-25560-4717@http.sourceware.org/bugzilla/>
2020-08-02 15:43 ` delta512.dev at protonmail dot com
2020-08-02 15:46 ` delta512.dev at protonmail dot com
2020-08-02 15:48 ` delta512.dev at protonmail dot com
2020-08-02 15:51 ` delta512.dev at protonmail dot com
2020-08-09 20:33 ` tromey at sourceware dot org
2020-08-10 21:05 ` delta512.dev at protonmail dot com [this message]
2020-08-10 21:08 ` delta512.dev at protonmail dot com
2020-08-10 21:14 ` delta512.dev at protonmail dot com
2020-10-20  2:51 ` erickitten at gmail dot com
2020-12-13 13:15 ` ddresser at bmc dot com
2021-06-25 19:00 ` dahllunde at gmail dot com
2021-06-25 20:56 ` delta512.dev at protonmail 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-25560-4717-i1K19KOFkK@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).