public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "diskpoppy at proton dot me" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/29612] New: Does not follow child processes spawned with posix_spawn() Date: Sun, 25 Sep 2022 18:53:55 +0000 [thread overview] Message-ID: <bug-29612-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29612 Bug ID: 29612 Summary: Does not follow child processes spawned with posix_spawn() Product: gdb Version: 12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: diskpoppy at proton dot me Target Milestone: --- I'm using homebrew gdb 12.1 on macOS 11.6.4 I have "set follow-fork-mode child" I expected for gdb to follow the process spawned with posix_spawn Minimal program using posix_spawn (that spawns itself, but it could also spawn other executables): #include <spawn.h> #define NULL 0 extern char **environ; int main(int argc, char** argv) { if(argc > 1 && argv[1][0] == 'g') { return 1; } pid_t pid_this = 0; char * argv_this[] = {"test_program", "g", NULL}; posix_spawn(&pid_this, "/path/test_program", NULL, NULL, argv_this, environ); return 0; } -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-09-25 18:53 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-25 18:53 diskpoppy at proton dot me [this message] 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
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@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).