in reply to Re: Strategy to track failure...
in thread Strategy to track failure...

Then you can start adding a few prints at that point to work out why.
Or, if you don't mind the shotgun approach, Devel::DumpTrace will print variable values, too. It may be too verbose to be useful in some cases.

Replies are listed 'Best First'.
Re^3: Strategy to track failure...
by CarolinaPerler (Acolyte) on Jun 13, 2013 at 18:20 UTC
    BrowserUK and Toolic, thanks. I've used both of those before and they should help. Apparently, was having a brain cramp earlier and bothered y'all instead of thinking them up, myself.

    Lanx,
    - identical perl version.
    - identical modules installed.
    - Don't remember the results of tests during install.... 'Been a while. But, we're not in the habit of using modules that don't test out pretty cleanly.
    - Not my choice to use Win32::Lanman. That having been said, it seems to be widely used and stable.... (except for this wrinkle).
    - Hadn't thought about contacting the author. Good idea that I'll pursue if Devel::Trace and/or Devel::DumpTrace are not fruitful.


    Thanks all.
    Gives me plenty to chew on.
[reply]

In Section Seekers of Perl Wisdom