public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/24069] gdb on OSX Mojave hangs in darwin_decode_message
Date: Wed, 02 Feb 2022 12:26:17 +0000 [thread overview]
Message-ID: <bug-24069-4717-oVhD3Plp5U@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24069-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24069
--- Comment #36 from Simon Marchi <simark at simark dot ca> ---
(In reply to Louis He from comment #35)
> Hi all,
>
> I am new to the GDB community and would like to contribute to this bug
> report. The bug still persists in the latest GDB 11.2 release. Based on the
> change from DomQ:
> https://github.com/domq/homebrew-gdb/blob/master/Formula/gdb.rb
>
> I am not sure why the changes (from line 137 - 178) in the above link is not
> included in the latest GDB release.
>
> I tried to move that part of the code to the latest GDB 11.2 and most of the
> time, the GDB on the darwin machine works. The modified source code locates
> in my GitHub Repo: https://github.com/Louis-He/gdb_darwin_hang_fix
>
> I have tested it on my Intel-based Macbook pro with Mac OSX 12.2.
>
> Best,
> Louis
Can you please provide a patch that applies on master? The latest attempt, I
wasn't able to apply the patch on master.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-02-02 12:26 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
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 [this message]
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-oVhD3Plp5U@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).