So many, but my favorite
was debugging what looked like a networking problem on a multi-player game.
First step: compile with debug enabled, install on one node.
Next step: scratch head as _everything_ falls over.
Look at user code, which did what amounted to a Remote Procedure Call by slopping a struct into a datagram and sending it. The first field of the struct was a function pointer, so the receive routine was essentially
Grab four bytes from the head of the datagram.
JSR to the code at that address, passing a pointer to the remainder.
On return, build a reply packet with the (integer only) return value, and send it back.
This "works" when every node is running exactly the same code. Not so much when foo() on one node is at a different address than foo() on another. Like, say, if the debug compile disables some optimization and code shifts.
Biting the hand that feeds IT
