in reply to
In short, you can't. The only thing you can do is to attempt to detect the
presence of the debugger (and any modules of the B:: namespace) and terminate your script if found. This is not as trivial as it might seem.
Additionally, you'd need to at least obfuscate things sufficiently, so that people will
give up before they succeed (for example because it's just not worth it)...
The only way to make it reasonably difficult for people to work around
your mechanisms is to distribute a modified perl binary, statically
linked with the decrypting source filter module (written is XS). With anything else it's
trivial to get at your decrypted Perl source and simply disable the debugger detection.
(But even with a modified perl binary, it's only a matter of how much
time someone is willing to invest to crack your 'protection'...)
Generally - as you can infer from the Anonymous Monk's reaction - trying to hide your source is widely frowned upon in the community, so you probably won't get a lot of help here...