RE: [GD-Windows] Win2K SP2 debugging slowdown?

[gaspow20 <gas...@nw...>]

Debug strings are passed to the debugger via a message queue of some
kind. There is no blocking issue involved that would slow down the game
- in other words, the game is never waiting for the debugger to catch
up. That's why the debugger can drop debug strings when it gets flooded.

The API function and queueing code is probably just really slow.
Short-circuits if no debugger is attached too.

> -----Original Message-----
> From: gam...@li...
> [mailto:gam...@li...] On
> Behalf Of Tom Forsyth
> Sent: Wednesday, October 03, 2001 8:42 AM
> To: GDWindows
> Subject: RE: [GD-Windows] Win2K SP2 debugging slowdown?
>
>
> [grrr... reply-to-person thing is getting annoying now]
>
> The debugger sets up a debug string handler that is usually
> very very slow. So if you're outputting a lot of info to the
> debug output, that will cause serious slowdowns when the
> debugger is active. Remember that DirectX also throws a lot
> of stuff into the debug stream if you have the debug level set high.
>
> Tom Forsyth - Muckyfoot bloke.
>
> What's he up to now (and can I have a go)?
> http://www.eidosinteractive.com/downloads/search.html?gmid=86