From: Steve L. <st...@fu...> - 2004-10-29 08:31:44
|
>Arguably, the way to do this sort of thing would be to just call >OutputDebugString() with whatever output you have. This will show up in >a debugger, if one is attached, or else in the system debugger, if one >exists. In a general library, and even moreso a compiler library, >trying to guess how to get the debug information to a human directly >will be wrong at least half the time, which is a mistake that library >writers don't have the liberty to make. Very good point! You may even still be able to stick a VT100 terminal on COM1 to see the output ;-) I was also thinking that perhaps assert should not terminate for similar reasons (but that is a mute point). The free tool debugview for sysinternals[1] is excellent if you do not have a suitable debugger to capture output. From trial the CRTDLL _assert used does not output to the debug stream, it just gets lost. The exit code 3 is returned though. Steve Lee 1: http://www.sysinternals.com/ntw2k/freeware/debugview.shtml Steve Lee --------- PowerTalk: free speech for your PowerPoint presentations at www.fullmeasure. co.uk |