[Lldb-commits] [PATCH] D134642: Propagate FORK events back to client

2023-01-10 Thread Jim Ingham via Phabricator via lldb-commits
jingham added a comment. Note, IMO the better solution to the problem of how to follow parent & child over a fork is to implement another "follow-fork" mode: "both" that when it sees the fork event, creates a separate target for the child process, and sets lldb debugging both. Then the user co

[Lldb-commits] [PATCH] D134642: Propagate FORK events back to client

2023-01-10 Thread Jim Ingham via Phabricator via lldb-commits
jingham requested changes to this revision. jingham added a comment. This revision now requires changes to proceed. First off, Is there a meaningful distinction between "fork" and "clone" in this context? we call the act whereby a process generates a child process a fork everywhere else in lldb

[Lldb-commits] [PATCH] D134642: Propagate FORK events back to client

2022-09-26 Thread Iryna Shakhova via Phabricator via lldb-commits
irinasha created this revision. Herald added a subscriber: emaste. Herald added a project: All. irinasha requested review of this revision. Herald added a project: LLDB. Herald added a subscriber: lldb-commits. We want to allow the client to detect when the process forks and to attach the debugge