in reply to Pentesting tool

and because no-one else has mentioned it yet: always use strictures (use strict; use warnings; - see The strictures, according to Seuss).

True laziness is hard work

Replies are listed 'Best First'.
Re^2: Pentesting tool
by Sketch- (Initiate) on Jul 05, 2011 at 02:49 UTC

    Ok thanks everyone, I'll start trying to solve these sorts of problems by returning the error messages and working with that.

    Also yeah, I used to use strict and warnings but then i kept getting syntax errors when I did.

    Probably cause my code failed but anyway. Thanks

      Those errors were telling you important stuff. Ignoring anything of that nature that can help resolve issues will make your life much more frustrating rather than less. The 'wierd error' at the heart of your OP is a case in point where you were being provided with exactly the information you needed to diagnose and solve a real problem. I strongly recommend that you reinstate strictures and fix your code to correct any problems they reveal.

      True laziness is hard work

      I used to have a similar problem with my car. Until recently, the oil low-pressure warning indicator would come on whenever I drove my car. This made me anxious. I put a piece of black tape over the indicator and now I never see it come on. I drive my car without a care in the world, but I wonder: Is there anything else I should be considering?