[Boost-testing] Re: Re: build_monitor - making it work better

From: Carl Daniel (cpdaniel_at_[hidden])
Date: 2005-03-16 23:16:05

Rene Rivera wrote:
> At a minimum CodeWarrior and GCC spawn children. And bjam itself runs
> it's actions in a child shell, for which the shell would spawn
> children. As a concrete example for CW it would go something like:
>
> python.exe
>   bjam.exe
>     cmd.exe
>       mwcc.exe (cw compile)
>     cmd.exe
>       mwcc.exe (cw link)
>         mwld.exe
>     cmd.exe
>       foo_test.exe
>     cmd.exe
>       bar_test.exe

Sounds like handling all child processes is a must if it's to work for 
anything other than test running (and maybe even for that).

I'll do some investigating into how much it complicates matters to debug 
child processes as well (I know it can be done - windbg does it afterall).

-cd