caustik's blog

programming and music

Painless Debug Console

with 18 comments

I have had the pleasure of writing a pretty large number of apps for Windows. There are a few things that I have learned, over time, that have really helped to improve my productivity. One of those things is a basic debug console.

Typically, a debug console is handy – go figure – while you’re debugging. Once you have a release quality build, you won’t want the debug console hanging around anymore.

This is one of those snippets of code that, while brutally simple, is rather non-obvious and most people don’t know of.

    freopen("CONOUT$", "wt", stdout);

    SetConsoleTitle(L"MyApp : Debug Console");


    printf(" MyApp Debug Console\n");

Basically this code, if debug trace preprocessor is set (add MYAPP_DEBUG_TRACE to your preprocessor settings), will allocate a nice little debug console window, change the title, set the font colors, and redirect standard output to the console.

This snippet of code can be added to any Win32 application, and gives you the instant capability to spit out oodles of delicious debugging data. Typically, I combine this method with something along these lines:

#ifdef __cplusplus
inline void null_func(char *format, ...) { }
#define DbgEmpty null_func
#define DbgEmpty { }
/* Debug Trace Enabled */
#define DbgPrintf printf
/* Debug Trace Disabled */
#define DbgPrintf DbgEmpty

Now, you can use the function “DbgPrintf” just as if it was “printf” – and it will compile away to nothing in a release mode build!

Written by caustik

October 24th, 2006 at 5:51 am

Posted in Programming

Tagged with

18 Responses to 'Painless Debug Console'

Subscribe to comments with RSS or TrackBack to 'Painless Debug Console'.

  1. Hi there!

    I like your work a lot, especially the neato idea you did with CxBx. This is also very useful to me, as I have one such debug console permanently in my application, and when releasing I turn it off in the DevCpp’s options. This is a much cleaner solution (but why am I telling you this when you know it?)

    Well, nuff nonsense talk, I just wanted you to know that I appreciate it a lot πŸ˜‰


    27 Oct 06 at 9:06 pm

  2. Why not just OutputDebugString() and catch with SysInternals’ DebugView (or similar)?


    12 Nov 06 at 12:26 am

  3. I can think of at least three problems with OutputDebugString:

    1) In release mode, the debugging strings will still exist in the binary.
    2) In release mode, the code (and associated overhead) will still exist in the binary.
    3) It is necessary to run an additional, separate, tool – e.g. DebugView.

    You can also expand this method easily to pipe to a file, for example.

    If you prefer OutputDebugString, anyway, you could at still use DbgPrintf, but when creating the #define, wrap OutputDebugString instead of printf. This will prevent 2 of the issues I listed.


    12 Nov 06 at 2:53 am

  4. I actually prefer having it in a separate process. It also provides more features, like a large scrollable buffer, GUI, and more. And of course, conditional #defines work for that too. I wouldn’t leave debug info in a final build! πŸ™‚


    13 Nov 06 at 12:00 am

  5. I’m not a programmer i’m a poor neuroscientist but i’d just like to say that i read your blog and i really like it it makes me smile a lot!


    21 Nov 06 at 12:43 am

  6. You should try to make a tema work with the Xeon staff.


    17 Jan 07 at 6:02 pm

  7. I just happened to find your tip when I was searching for the reason why my application was not outputting printfs (turns out it’s a Win32 app and not a console, so there was no “output”, so to speak).

    Your tip has been very helfpul – thanks!


    18 Apr 07 at 3:02 am

  8. GREAT! just what I was looking for!


    20 Apr 07 at 9:25 am

  9. Thanks sir caustik. I’m using this in my emulator πŸ˜›


    24 Jun 07 at 6:16 pm

  10. hi caustik, I’ve just stumbled across your website, and this article. Its just what I’m looking for!
    Although – I think I may be missing something. I pasted your code snippet it into my Win32 app. I’m generating the console OK, and the title sets fine, but the printf’s do not produce any output.
    My app is written in C++, so I tried
    std::cout << “blah”; but that doesn’t produce output either… am I missing something?


    3 Oct 07 at 2:01 am

  11. That is strange. What compiler and OS is this on? Are you using cygwin? (I have only tested this one MSVC)


    3 Oct 07 at 2:13 am

  12. I just found this explanation on

    “It is important that you create your console before you create the main window. If you don’t, the console will still be created, but your debugging messages send with _cprintf() will not arrive in your console. I couldn’t figure out why it is like this, only that it is like this.”

    This fits, I’m not creating the console until after my main window has been created.


    3 Oct 07 at 2:36 am

  13. Just saw your comment – its Windows XP and using MS Visual Studio 2005 – Express Edition.


    3 Oct 07 at 2:37 am

  14. Actually, no matter where in my application I put the code snippet, I still don’t get any debug output. I think my original post about creating the console before creating the main window was wrong perhaps.


    4 Oct 07 at 2:33 am

  15. This is great! Thanks.


    11 Oct 08 at 5:26 pm

  16. After reading this article, I feel that I need more info. Can you suggest some more resources ?


    24 Apr 09 at 4:00 am

  17. One of the most useful snippets I’ve ever found. Thank you πŸ™‚


    26 Apr 09 at 1:17 pm

  18. Hi
    great snippet, worked immediately!!
    On some pages they tell you on ten pages how to redirect the printf command.
    For people who have no time for nerdy talking… this worked in 10 seconds.
    Thanks a lot!!


    15 Jul 09 at 7:33 am

Leave a Reply