From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id AE310385781D; Mon, 29 Mar 2021 21:51:40 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AE310385781D From: "gerrypipes at hotmail dot com" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 10.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gerrypipes at hotmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gdb-prs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-prs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Mar 2021 21:51:40 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D27663 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 outp= ut (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=20 ../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. --=20 You are receiving this mail because: You are on the CC list for the bug.=