GCC Undefined Behavior
From feross.org:
Check out this little GCC gem that I just discovered read about.
...
When GCC identified bad C++ code, it tried to start NetHack, Rogue, or Towers of Hanoi. Failing all three, GCC printed out a cryptic error message. Wow.
This just goes to show you that when the official C++ specification talks about undefined behavior, they mean business:
[Undefined behavior is] behavior, such as might arise upon use of an erroneous program construct or erroneous data, for which the Standard imposes no requirements
No requirements indeed.
I found this immensely entertaining. "Undefined Behavior" indeed. Also, not surprising that those who have to use C++ could stand have some humor injected into their otherwise painful lives (I kid... kind of).