[Lldb-commits] [PATCH] D100208: [lldb] [Process/Linux] Report fork/vfork stop reason to client

mgorny updated this revision to Diff 337238. mgorny added a comment. Rebase. Store `mainloop` arg of the original process, and pass it to the children to make them independent of the 'main' process. CHANGES SINCE LAST ACTION https://reviews.llvm.org/D100208/new/

[Lldb-commits] [PATCH] D100208: [lldb] [Process/Linux] Report fork/vfork stop reason to client

mgorny updated this revision to Diff 336670. mgorny added a comment. Report vfork-done stop to the client as well. CHANGES SINCE LAST ACTION https://reviews.llvm.org/D100208/new/ https://reviews.llvm.org/D100208 Files: lldb/source/Plugins/Process/Linux/NativeProcessLinux.cpp

[Lldb-commits] [PATCH] D100208: [lldb] [Process/Linux] Report fork/vfork stop reason to client

mgorny updated this revision to Diff 336657. mgorny added a comment. Copy software breakpoints to the forked process, to future-proof this patch for breakpoint support (I suppose there's no point in splitting it more). Add `GetSupportedExtensions()` to actually enable the new code. CHANGES

[Lldb-commits] [PATCH] D100208: [lldb] [Process/Linux] Report fork/vfork stop reason to client

mgorny added a comment. Ok, found the culprit. Now it's ready ;-). CHANGES SINCE LAST ACTION https://reviews.llvm.org/D100208/new/ https://reviews.llvm.org/D100208 ___ lldb-commits mailing list lldb-commits@lists.llvm.org

[Lldb-commits] [PATCH] D100208: [lldb] [Process/Linux] Report fork/vfork stop reason to client [WIP]

mgorny added a comment. This is the final piece for moving minimal fork/vfork support to gdb-remote protocol. However, for some reason (unlike the original code in D99864 ), it crashes on random assertions about `m_enabled_extensions` value — probably memory

[Lldb-commits] [PATCH] D100208: [lldb] [Process/Linux] Report fork/vfork stop reason to client [WIP]

mgorny created this revision. mgorny added reviewers: labath, emaste, krytarowski. mgorny requested review of this revision. Enable reporting fork/vfork events to the client when supported. This switches from implicit server-side handling to client-controlled gdb-remote protocol exchange.