In certain CTF, for example SQL injection challenges, the target webpage returns 418 to make more difficult the success of blind injection scripts (they will fail randomly, so you have to check that the return code is weird and retry)
The linux button is not visible on the top if your resolution is too narrow, It's the least clicked button so I chop it off first. As for whether this is a good idea probably not.
Yes, I finally decided to go with the BSD license, since I'd like to enable people to benefit from this, which might mean being able to add new tests without revealing the model answer :)
That kind of depends. They can also happen not because you attached a debugger but because you set a break point in a particularly unfortunate location.
GDB reverse debugger is very slow as it is saving the execution state after every instruction executed.
There is a commercial plugin for GDB reverse debugger: UndoDB. It is much faster than just GDB (they claim only 1.7x slowdown), but unfortunately not very stable for the product I'm working on.
I'm a co-founder of the company. Lots of stability improvements over the past year or so: I'd urge you to try it again. Particularly v4 beta. Send email to beta@undo-software.com to get a beta license.
I'd never claim it's perfect: it's software after all, and the fact most software has bugs is why we have a business in the first place ;) But we're used by some pretty hardcore folk these days, including Cadence, NASA, and some of the biggest banks in the world. And the PyPy guys seem pretty happy :) Oh, and of course, if you do find issues, please do report them to support@undo-software.com -- then we can fix them.