public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "levraiphilippeblain at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/24069] gdb on OSX Mojave hangs in darwin_decode_message Date: Thu, 25 Jun 2020 12:35:30 +0000 [thread overview] Message-ID: <bug-24069-4717-F5QfMQO08l@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-24069-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=24069 Philippe Blain <levraiphilippeblain at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |levraiphilippeblain at gmail dot c | |om --- Comment #6 from Philippe Blain <levraiphilippeblain at gmail dot com> --- I tried building 8.3.1 on macOS 10.15.5 (latest Catalina), and about half of the time GDB hangs just as kemlath and timothee cour describe. I also attached LLDB and GDB is indeed stuck in `darwin_decode_message`. If I recompile with the change that kemlath suggests, diff --git a/gdb/darwin-nat.c b/gdb/darwin-nat.c index 8c34aa8a3f..d30374b673 100644 --- a/gdb/darwin-nat.c +++ b/gdb/darwin-nat.c @@ -1151,7 +1151,7 @@ darwin_decode_message (mach_msg_header_t *hdr, res, wstatus); /* Looks necessary on Leopard and harmless... */ - wait4 (inf->pid, &wstatus, 0, NULL); + wait4 (inf->pid, &wstatus, WNOHANG, NULL); inferior_ptid = ptid_t (inf->pid, 0, 0); return inferior_ptid; then a little more than half the time I get "During startup program terminated with signal ?, Unknown signal" and the rest of the time it works fine. I'll try with 9.1 and 9.2. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-06-25 12:35 UTC|newest] Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-24069-4717@http.sourceware.org/bugzilla/> 2020-04-13 21:08 ` rostyslav.skrypnyk at gmail dot com 2020-06-25 12:35 ` levraiphilippeblain at gmail dot com [this message] 2020-06-26 23:01 ` levraiphilippeblain at gmail dot com 2021-04-07 17:13 ` dominique at quatravaux dot org 2021-04-07 17:59 ` simark at simark dot ca 2021-04-07 18:11 ` dominique at quatravaux dot org 2021-04-07 19:18 ` dominique at quatravaux dot org 2021-04-08 11:26 ` dominique at quatravaux dot org 2021-04-08 13:43 ` simark at simark dot ca 2021-04-08 16:11 ` dominique at quatravaux dot org 2021-04-08 16:59 ` dominique at quatravaux dot org 2021-04-08 17:26 ` simark at simark dot ca 2021-04-08 19:18 ` dominique at quatravaux dot org 2021-04-09 13:35 ` kemlath at gmail dot com 2021-04-19 16:03 ` tromey at sourceware dot org 2021-07-04 14:36 ` jordan.mandel at live dot com 2021-07-05 2:03 ` simark at simark dot ca 2021-07-06 23:49 ` Samuel.r.warner at me dot com 2021-07-06 23:57 ` simark at simark dot ca 2021-07-07 0:24 ` Samuel.r.warner at me dot com 2021-07-07 3:28 ` Samuel.r.warner at me dot com 2021-07-07 22:48 ` Samuel.r.warner at me dot com 2021-07-07 22:52 ` Samuel.r.warner at me dot com 2021-07-08 16:02 ` Samuel.r.warner at me dot com 2021-07-08 20:51 ` Samuel.r.warner at me dot com 2021-07-08 21:20 ` dominique at quatravaux dot org 2021-07-08 21:48 ` simark at simark dot ca 2021-07-09 2:38 ` Samuel.r.warner at me dot com 2021-09-12 21:48 ` brobecker at gnat dot com 2021-10-04 22:02 ` rachelmheaton at gmail dot com 2021-11-21 14:41 ` simark at simark dot ca 2021-11-21 17:21 ` Samuel.r.warner at me dot com 2021-11-22 15:23 ` dominique at quatravaux dot org 2021-11-27 3:17 ` Samuel.r.warner at me dot com 2022-02-02 5:49 ` siwei.he at mail dot utoronto.ca 2022-02-02 12:26 ` simark at simark dot ca 2022-02-02 19:39 ` siwei.he at mail dot utoronto.ca 2022-02-02 19:40 ` siwei.he at mail dot utoronto.ca 2022-02-02 19:55 ` siwei.he at mail dot utoronto.ca 2022-02-02 19:55 ` siwei.he at mail dot utoronto.ca 2022-02-02 19:56 ` siwei.he at mail dot utoronto.ca 2022-02-02 20:00 ` siwei.he at mail dot utoronto.ca 2022-02-02 20:03 ` siwei.he at mail dot utoronto.ca 2022-02-02 20:04 ` siwei.he at mail dot utoronto.ca 2022-02-16 14:29 ` levraiphilippeblain at gmail dot com 2022-02-19 16:03 ` cvs-commit at gcc dot gnu.org 2022-02-28 18:35 ` simark at simark dot ca 2022-03-10 12:12 ` saagar at saagarjha 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-24069-4717-F5QfMQO08l@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: linkBe 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).