There are several possibilities. Which one is the case will depend on many variables -- including how well-informed the user is, what sort of code you write, and how secure you are that your configuration is correct.
The first possibility is that the user was incorrect, and the code in question was not perl at all, but javascript, and the debugger was Microsoft Visual InterDev, or Microsoft Visual Script Editor, not Visual Basic. (It's possible that VS 2003 has unified them, but last I looked, they were sepperate tools.)
The second possibility is that you're writing an ASP-based (or similar -- I forget what the look-alike Apache-based framework is called, or even if there is one) page, and somehow your script got through to the browser, and was interpreted as incorrect javascript (see above).
The third is that he's just rattling your chain.
The fourth is that you aren't using a CGI-ish script at all, but rather are using a local script, and somehow, interdev, or even VB, managed to notice that it died, and debug it.
Note that all of the above cases contain at least one miscommunication, so you may be best getting him to repeat it with you there, or at least take a screenshot.
In reply to Re: VB debugging my Perl Scripts on user comp? help! Security issue!
by theorbtwo
in thread VB debugging my Perl Scripts on user comp? help! Security issue!
by Stenyj
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |