You are misinterpreting that page (it's meant for users of GCC, not developers of it), and based on your previous very lengthy post, misunderstanding how most software in general works, including compilers and even the Lua language. I don't really know where to start with helping you, as you are VERY far off the mark on almost every point you've made, but I do know that we are incredibly off-topic in this thread. If you want, you can PM me and I can try to set you on the right track, but it is likely a big waste of time unless you intend to learn software development.

The bottom line is that GCC has a pretty decent mechanism to detect its own problems and trigger a handler that results in a program abort along with diagnostic instructions. ESO has the same thing, though it's actually a much better one (your characterization of the ESO crash handler and the assumptions you made are almost completely wrong, btw). Many pieces of software have this feature, including every single piece of software that links to abrt (there are thousands of such things in a typical Fedora software stack, for example.) Those actually include backtrace analysis to combine like causes together and associate them with bug fixes (I've used this in the past, and you have to be careful about false positives here.)

Like I said, though, we're off-topic. PM me if you'd like further information.

Just imagine your bank treating you like this, and then cry. Or laugh