<html><div style='background-color:'><P>Rob,</P>
<DIV class=RTE>
<P>Finally, things calmed down so I could do some additional research and I found a way to get the Perl Debugger to run noninteractively with AutoTrace turned on. The trace for the line of code that tries to set the proxy URL is attached in a text file.</P>
<P>Note, I only sent the end of the trace for the code lines I figured was important. If you want to see the whole thing, let me know (it's pretty big).</P>
<P>thx, Jason<BR><BR></P><BR><BR><BR>From: Rob Nagler <nagler@bivio.biz><BR>Reply-To: boulder-pm@pm.org<BR>To: boulder-pm@pm.org<BR>Subject: Re: [Boulder.pm] LWP::UserAgent question<BR>Date: Thu, 21 Jul 2005 14:00:12 -0600<BR><BR>Jason Van Slyke writes:<BR>> And then diagnostics chatters on for hundreds of lines. I apologize,<BR>> but I am not fluent in the use of the perl debugger. But if you give a<BR>> brief description of what I should have done, there is a pocket guide<BR>> to the perl debugger around here somewhere and I'll get it<BR>> done.<BR><BR>diagnostics is probably making the chatter. Have you tried:<BR><BR> perl program 2>diag.out<BR> splain diag.out<BR><BR>Alternatively, you could:<BR><BR> perl -Mdiagnostics=-traceonly my_script.pl<BR><BR>And send me the stack
trace.<BR><BR>Rob<BR><BR><BR><BR>_______________________________________________<BR>Boulder-pm mailing list<BR>Boulder-pm@pm.org<BR>http://mail.pm.org/mailman/listinfo/boulder-pm<BR></DIV></div></html>