krytarowski added inline comments.
================
Comment at:
lldb/packages/Python/lldbsuite/test/tools/lldb-server/TestGdbRemote_vContThreads.py:68-72
+ "read packet: $vCont;C{0:x}:{1:x};C{0:x}:{2:x}#00".format(
+ lldbutil.get_signal_number('SIGUSR1'),
+ threads[0], threads[1]),
+ {"direction": "send", "regex": r"^\$W00#b7$"},
+ ], True)
----------------
mgorny wrote:
> labath wrote:
> > It might be nice to actually verify how many signals did the process
> > receive here. I guess you could do that by just checking the output of the
> > signal handler.
> I've tried but it claimed to timeout before receiving any output. I suspect
> the interrupt terminates `sleep()` in thread, and they exit before the signal
> handler manages to get run. Or maybe I was doing something wrong.
There is a bug in the kernel with `sleep()` that it does not return EINTR when
interrupted. It shall be fixes as it is imho fatal.
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D70022/new/
https://reviews.llvm.org/D70022
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
