[Lldb-commits] [lldb] Ptrace seize dead process (PR #137041)

2025-04-24 Thread Jacob Lalonde via lldb-commits
Jlalond wrote: > I think the tricky part is that (in both cases) the user might legitimately > want to let the process exit, and "continue" is the normal way to do that, so > I don't think we'd want to just error out of the continue command (or from > the vCont packet). I think what we'd want

[Lldb-commits] [lldb] Ptrace seize dead process (PR #137041)

2025-04-24 Thread Pavel Labath via lldb-commits
labath wrote: We already have one piece of "status" parsing code in `source/Host/linux/Host.cpp`. I think it'd be better to reuse that one. I'm slightly torn as to whether reuse Host::GetProcessInfo for this (and add a new field to ProcessInstanceInfo -- or possibly expand on IsZombie), or whe

[Lldb-commits] [lldb] Ptrace seize dead process (PR #137041)

2025-04-23 Thread Jacob Lalonde via lldb-commits
https://github.com/Jlalond updated https://github.com/llvm/llvm-project/pull/137041 >From a33b865302e0d489cc4426c038128d8dde47500e Mon Sep 17 00:00:00 2001 From: Jacob Lalonde Date: Tue, 22 Apr 2025 16:35:00 -0700 Subject: [PATCH 1/2] Create proc status reader --- .../Plugins/Process/Utility/

[Lldb-commits] [lldb] Ptrace seize dead process (PR #137041)

2025-04-23 Thread Jacob Lalonde via lldb-commits
https://github.com/Jlalond created https://github.com/llvm/llvm-project/pull/137041 This the actual PR to my [SEIZE RFC](https://discourse.llvm.org/t/rfc-ptrace-seize-when-attaching-to-dead-processes/85825/8). This is currently the bare bones on seizing a dead process, and being able to attac