It's javascript injection.<p>But the clever method of finding the result seems as encouraging as clever methods for finding null pointers. Sure, try initializing your memory beforehand to a call to the debugger - (or just 0 and have that trigger the usual exception handling). Sure you can do this but those null pointers keep popping up. I'd assume you could find analogy for SQL injection too.<p>I'm more interested in techniques which prevent this from happening to begin with. The clever techniques often only help you find stuff you have a good idea is already there.