public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "gerrypipes at hotmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27663] New: gdb hangs on New Thread ## of Process ## running on Big Sur
Date: Mon, 29 Mar 2021 21:51:40 +0000 [thread overview]
Message-ID: <bug-27663-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27663
Bug ID: 27663
Summary: gdb hangs on New Thread ## of Process ## running on
Big Sur
Product: gdb
Version: 10.1
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: gerrypipes at hotmail dot com
Target Milestone: ---
When running the latest gdb on Big Sur (macOS) I receive the following output
(gdb) run
Starting program: /Users/gpipes/test/a.out
[New Thread 0x#### of process ###]
This has happened before on earlier OS's but seemed to be a race condition or
could be resolved by going to an earlier version.
Running a local build of gdb as well using the instructions from "current" and
compiling as follows
../configure --disable-werror
make
causes the issue to happen.
It can be done on any program compiled with g++-10 (latest g++) or clang, I
have tried both, it doesn't seem to be unique to that.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-03-29 21:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 21:51 gerrypipes at hotmail dot com [this message]
2021-04-14 0:23 ` [Bug gdb/27663] " andrea at andreamoro dot net
2022-02-28 18:59 ` levraiphilippeblain at gmail 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-27663-4717@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).