labath added a comment.
(Actually, I don't think we do it for the main `Halt` operation (though maybe
we should) -- only for the SIGSTOPs send to individual threads when we're
performing an all-stop.)
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
labath added a comment.
Herald added a subscriber: JDevlieghere.
This still leaves the possibility of a race where the process stops on its own
while you're in the process of sending the signal, right?
I believe that on linux we handling this by checking the stopped events: If the
application
This revision was automatically updated to reflect the committed changes.
Closed by commit rGaed179f5f557: [lldb] [Process/FreeBSD] Do not send SIGSTOP
to stopped process (authored by mgorny).
Herald added a project: LLDB.
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
mgorny created this revision.
mgorny added reviewers: labath, krytarowski, emaste.
Herald added a subscriber: arichardson.
Herald added a project: All.
mgorny requested review of this revision.
Do not send SIGSTOP when requested to halt a process that's already
stopped. This results in the
