|There's more than one way to do things|
Re: Strategy to track failure...by BrowserUk (Pope)
|on Jun 13, 2013 at 14:49 UTC||Need Help??|
The first thing I would do is (install Devel::Trace if you don't already have it), and run the failing script like this:
When it stops (due to the throw Error::Simple($error);), the last few lines in the log will tell you where it had just been. It'll give you a starting point.
If you then do the same with the working code, you should be able to match up the logs from the entry point in NetLocalGroupEnum() and see where they diverge which should get you to the point of failure quickly.
Then you can start adding a few prints at that point to work out why.
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.