SERVICES Hi folks,

I've got a PerlEx script that grows on each iteration.  The script gets 
external data using SOAP::Lite, which in turn is using XML::Parser.  I 
suspect that the issues are in the SOAP-related code, as the rest of the 
script is old: the SOAP code is new, replacing Win32 COM calls.

Is it possible to attach any of the ActiveState debuggers (I've got all 
of them) to the PerlEx interpreter threads? 

Or any clever suggestions for simulating the PerlEx environment from the 
command-line, making the script execute multiple times, so that I can 
run it in a debugger normally? 

Or any other leak-checking modules to try?  Devel::LeakTrace doesn't 
seem to exist for Windows and Devel::ObjectTracker causes perl.exe to bomb.

Cheers,
Richard

P.S. I've intentionally cross-posted to the ActivePerl and PerlEx lists, 
as I'm hoping some friendly folks may have relevant experience to share 
from similar persistent environments like FastCGI and mod_perl.

-- 
*** Richard A. Wells, raw@[...].com, +1.978.371.7425
*** Reality And Wonder, http://www.raw.com/


_______________________________________________
PerlEx mailing list
PerlEx@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs