[DeltaZulu]

Couldn’t be Java. The gun was way too fast. Couldn’t be C# either. Gun’s probably aren’t supported hardware. Sounds more like unmanaged code like C++. This whole incident adds a completely new dimension to the term ‘invalid pointer’.

[familyop]

"Couldn’t be Java. The gun was way too fast. Couldn’t be C# either. Gun’s probably aren’t supported hardware. Sounds more like unmanaged code like C++. This whole incident adds a completely new dimension to the term ‘invalid pointer’."

I was joking. ...could even have been assembly. Most civilian "embedded" (custom device oriented) projects continue to find developers who are stuck in C, although that might change as machines get much faster soon, and more projects, much larger.

And you probably already know that runaway processes can be caused by many other things, too: bad peripheral devices, climate conditions,...

[familyop]

"This whole incident adds a completely new dimension to the term ‘invalid pointer’."

Those can be really hard to catch before production use--especially without peer code reviews and much runtime testing.