http://wiki.armagetronad.org/api.php?action=feedcontributions&feedformat=atom&user=216.80.66.146 2026-10-16T04:24:00Z User contributions MediaWiki 1.44.2 http://wiki.armagetronad.org/index.php?title=Error_Handling&diff=18207 2007-05-13T03:44:42Z

<p>216.80.66.146: </p> <hr /> <div>* tASSERT: assertions, active in debug mode only. like c's assert(). Fatal program halt if the argument is false.<br /> * tVERIFY: the same, but active also in optimized mode.<br /> * st_PresentMessage(): displays/prints an error/warning message with a short caption (gets to be a title) and a longer message text. Execution continues after that.<br /> * st_PresentError(): the same, but exits with a fatal error after it's done.<br /> <br /> * tERR_WARN: prints a warning message on the console with reference to the function and source file it came from.<br /> * tERR_MESSAGE: similar, but uses st_PresentMessage() which makes the message more visible.<br /> * tERR_ERROR: still the same as tERR_WARN, but aborts.<br /> * tERR_ERROR_INT: internal error notifier. Same as tERR_ERROR, but asks to send bug reports.<br /> <br /> st_Breakpoint(): does nothing useful, but in GDB, a breakpoint is set there, so if you want a breakpoint you don't have to reset on every debug session, call this.<br /> <br /> The rest is flow control output stuff and is much less useful than anticipated. Either it gives too little or too much information. I don't use it any more.<br /> <br /> Error: Rage 128 timed out... exiting (go to detail settings and turn off textures...problem solved)</div>

216.80.66.146