[Lldb-commits] [PATCH] D120320: [lldb/driver] Fix SIGTSTP handling

[David Spickett via Phabricator via lldb-commits]

DavidSpickett added a comment.

I think I mostly get it and the code looks fine, but my signal foo is weak so @mgorny should give a second look.

> we use raise to send the signal, which makes sure it gets delivered to the thread which is running the handler

https://man7.org/linux/man-pages/man3/raise.3.html says:

> If the signal causes a handler to be called, raise() will return
> only after the signal handler has returned.

So what is going to be the "thread which is running the signal handler" here? Will all the lldb threads follow these steps of enter handler -> unregister handler -> raise until finally lldb as a whole sleeps until we get a continue and do the reverse?


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D120320/new/

https://reviews.llvm.org/D120320