public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/29612] Does not follow child processes spawned with posix_spawn() Date: Sat, 01 Oct 2022 16:09:35 +0000 [thread overview] Message-ID: <bug-29612-4717-UAs3Ro1z6Y@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29612-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29612 Tom Tromey <tromey at sourceware dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot org Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Last reconfirmed| |2022-10-01 --- Comment #1 from Tom Tromey <tromey at sourceware dot org> --- I don't think anybody has implemented follow-fork or multi-inferior for macOS. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2022-10-01 16:09 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-25 18:53 [Bug gdb/29612] New: " diskpoppy at proton dot me 2022-09-25 18:56 ` [Bug gdb/29612] " diskpoppy at proton dot me 2022-09-25 19:45 ` diskpoppy at proton dot me 2022-10-01 16:09 ` tromey at sourceware dot org [this message]
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-29612-4717-UAs3Ro1z6Y@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).