From: Simon Marchi <simon.marchi@polymtl.ca>
To: Sam Warner <samuel.r.warner@me.com>
Cc: gdb@sourceware.org
Subject: Re: GDB and MacOS 11.4/BigSur
Date: Sat, 26 Jun 2021 20:51:05 -0400 [thread overview]
Message-ID: <5180de47-136f-bad7-9f83-78ac02a323c6@polymtl.ca> (raw)
In-Reply-To: <9717BBC8-70FA-47DD-8C62-33018D746003@me.com>
On 2021-06-26 7:27 p.m., Sam Warner wrote:
> Hi Simon,
> :), perfect, how can I help?
Specifically, with the bug you reported, you would need to figure out
why the global current_thread_ is nullptr at the point inferior_thread
is called. In fact, all this happens before you tried to run anything,
so it's expected that there is no current thread: there are no threads
at all yet.
So, try to get a backtrace so we at least know which inferior_thread
call that is. You can try to attach a working GDB to the broken GDB
while it's at the "would you like to create a core dump" question. If
GDB is too broken, you can try lldb, whatever works.
Once we have that, we figure out a solution :).
Simon
next prev parent reply other threads:[~2021-06-27 0:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-26 18:40 Sam Warner
2021-06-26 23:08 ` Simon Marchi
2021-06-26 23:27 ` Sam Warner
2021-06-27 0:51 ` Simon Marchi [this message]
2021-06-27 4:00 ` Simon Marchi
2021-06-27 20:32 ` Sam Warner
2021-06-27 22:27 ` Simon Marchi
2021-06-27 22:44 ` Sam Warner
2021-06-28 0:48 ` Simon Marchi
2021-06-28 18:10 ` Sam Warner
2021-06-28 21:51 ` Sam Warner
2021-06-29 0:03 ` Sam Warner
2021-06-29 0:29 ` Sam Warner
2021-06-29 1:34 ` Sam Warner
2021-06-29 1:44 ` Sam Warner
2021-06-29 14:04 ` Simon Marchi
2021-06-29 14:38 ` Sam Warner
2021-06-29 14:43 ` Simon Marchi
2021-06-29 14:45 ` Sam Warner
2021-06-29 14:59 ` Sam Warner
2021-06-29 15:17 ` Sam Warner
2021-06-29 15:23 ` Simon Marchi
2021-06-30 21:29 ` Sam Warner
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=5180de47-136f-bad7-9f83-78ac02a323c6@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb@sourceware.org \
--cc=samuel.r.warner@me.com \
/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).