[Mpls-pm] MIME::Base64 on Windows

James.FitzGibbon James.FitzGibbon at target.com
Tue Jun 8 10:18:21 CDT 2004


This is from the perldebug manpage:

       If your rc file contains:

         parse_options("NonStop=1 LineInfo=db.out AutoTrace");

       then your script will run without human intervention, putting
trace
       information into the file db.out.  (If you interrupt it, you'd
better
       reset "LineInfo" to /dev/tty if you expect to see anything.)

There's also Devel::Trace:

http://search.cpan.org/~mjd/Devel-Trace-0.10/

-----Original Message-----
From: mpls-pm-bounces at pm.org [mailto:mpls-pm-bounces at pm.org] On Behalf
Of Dan Oelke
Sent: Tuesday, June 08, 2004 10:11 AM
To: Gypsy Rogers
Cc: Mpls-pm at pm.org
Subject: Re: [Mpls-pm] MIME::Base64 on Windows


One more idea - I don't know enough here to say if this is possible. 
So, maybe this will help Gypsy, *and* hopefully it will help me learn
something new about perl. ;-)

Is there a way to have the perl interpreter/compiler spit out a line as
it goes into each function. Kind of like an strace but for every
function call.  That would at least give you an idea of what is causing
the hang up.

Dan

Gypsy Rogers wrote:

>I don't believe windows machines have error logs that or
>they hide them in some obscure spot. I've already tried squelching the 
>buffer to no avail.
>
>And carping gives me nothing.
>
>Running the script from command line with use MIME::Base64; 
>uncommmented gives no output, running it commented gives me my output.
>
>On Mon, 7 Jun 2004 13:56:21 -0500
> Josh Jore <josh at grenekatz.org> wrote:
>  
>
>>On Mon, Jun 07, 2004 at 01:31:40PM -0500, Gypsy Rogers
>>wrote:
>>}
>>} I didn't use CGI.pm because it was a quicky test script
>>to
>>} prove a point... when use MIME::Base64; is uncommented
>>the
>>} script times out, when it is commented out the script
>>works
>>} fine. The script I sent was my test not the actual
>>script
>>} which was too long and might have had other errors in
>>it.
>>
>>Well then perhaps you are "suffering from buffering" due
>>to an
>>error. Go search google using that phrase. See also
>>Carp::CGI
>>'fatalsToBrowser'. Further, see your error log to see if anything
>>showed up there.
>>
>>--
>>Josh
>>    
>>
>
>_______________________________________________
>Mpls-pm mailing list
>Mpls-pm at pm.org
>http://www.pm.org/mailman/listinfo/mpls-pm
>  
>

_______________________________________________
Mpls-pm mailing list
Mpls-pm at pm.org
http://www.pm.org/mailman/listinfo/mpls-pm




More information about the Mpls-pm mailing list