On Wed, Oct 24, 2012 at 10:59 AM, Benson Margulies <[email protected]> wrote: > OK, that explains the forks, but not iterating infinitely in a loop > forking the top of the build (and all the interior pieces).
Can't really help there. Can only suggest running with -X and writing output to a file. Manually go through this and cull everything that is not telling you which plugin is running and why. You will be left with the call tree of the plugins. I'm assuming at this point it will be obvious what plugin is not behaving the way you expect it to. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
