ctest uses the kwsys utilities to launch and monitor sub-processes.
Theoretically, it goes like this, with variations in implementation
from platform to platform:
After a call to a kwsysProcessCreate function (which spawns a process
asynchronously and returns control to ctest), we loop while
Thanks.
Who knows about kwsys? I only need this on a couple of platforms and don't mind
doing it once for each.
Sent from my iPhone
On Jun 27, 2012, at 14:09, David Cole david.c...@kitware.com wrote:
ctest uses the kwsys utilities to launch and monitor sub-processes.
Theoretically, it
Never mind, I found it. SIGKILL is used. Oh well.
Sent from my iPhone
On Jun 27, 2012, at 14:54, Leif Walsh leif.wa...@gmail.com wrote:
Thanks.
Who knows about kwsys? I only need this on a couple of platforms and don't
mind doing it once for each.
Sent from my iPhone
On Jun 27,
I'd like to be able to get a backtrace when a test times out with ctest, so I
can analyze where the test was stuck, if at all.
I tried writing a fake test to tell me what signal ctest was using to kill a
timing out test, but it couldn't. I imagine this is because it uses SIGKILL
and I can't
