[torquedev] job stuck in E on Leopard

[Chris Samuel]

Hi Glen,

----- "Glen Beane" <glen.beane at gmail.com> wrote:

> I added a print statement to the top of the big for loop that should
> be calling sys_copy for the .o and .e files and the for loop only gets
> executed once, and I also had sys_copy create a file in /tmp uniquely
> named based on its pid, this contained the actual cp command that is
> being executed. I would see that sys_copy was being called for my .o
> file, but never for my .e file. Its like the child forked in
> req_cpyfile was exiting before it could loop onto the .e file, but
> like I said I confirmed that the same for loop just containing a
> simple print statement would loop over both .o and .e files

It'd be ugly, but you could have a separate printf
between each functional statement printing out __LINE__ so
you could see how far it got, and whether it was
consistent in its exiting ?

Does OSX have anything akin to strace so you could run
the mom in debug mode in the foreground and trace all
children to see if there were any unexpected signals ?

I don't suppose there's anything in the system logs either ?

cheers,
Chris
-- 
Christopher Samuel - (03) 9925 4751 - Systems Manager
 The Victorian Partnership for Advanced Computing
 P.O. Box 201, Carlton South, VIC 3053, Australia
VPAC is a not-for-profit Registered Research Agency