Click here to Skip to main content
13,405,390 members (57,844 online)
Click here to Skip to main content
Add your own
alternative version


39 bookmarked
Posted 10 Apr 2001

Using an output stream for debugging

, 24 Nov 2001
Rate this:
Please Sign up or sign in to vote.
How to create an output stream that writes to the debug terminal.


There are many different schools of how to debug a program (yeah, I know - write it correctly from the start), but whatever tools you prefer it is often very convenient just to use the printf approach. Well, since you are a modern C++ kind of person, you don't really want printf, you want to use an output stream, like cerr.

There's just one problem though, you are writing Windows applications, so there is no standard error output to write to. Not true, actually there is, and you've probably used many times already. When you use one of the TRACE macros, the result ends up in the Debug pane of Visual Studio. MFC goes through great pains to turn off all this debug output in Release builds, but it can often be very convenient to keep it.

Of course, you won't see any output in Visual Studio from a release build, but there are other programs that can capture this output. A good one is DebugView from Incidentially, if you start this program you'll probably see like a million messages from Internet Explorer. There you go, even Microsoft practise Release build debugging!

The problem

So, how to direct a standard output stream to the debug terminal? In general, the correct answer is to derive from streambuf and connect the new class to a normal ostream. In this way all stream inserters and manipulators work as expected. In this case we can save some work by deriving from stringbuf instead. So, without further ado, here's how to do it:

The code

First we include the needed headers.

#include <Windows.h>
#include <ostream>
#include <sstream>
#include <string>

Now for the real work: Since we are using a stringbuf we only need to override the sync function.

The sync method is what actually transfers the text in the put area to whatever output destination the streambuf uses, in this case by calling the API function OutputDebugString.

template <class CharT, class TraitsT = std::char_traits<CharT> >
class basic_debugbuf : 
    public std::basic_stringbuf<CharT, TraitsT>

    virtual ~basic_debugbuf()


    int sync()
        str(std::basic_string<CharT>());    // Clear the string buffer

        return 0;

    void output_debug_string(const CharT *text) {}

Next, I specialize the output routine so it calls the Ansi or Unicode API as appropriate.

void basic_debugbuf<char>::output_debug_string(const char *text)

void basic_debugbuf<wchar_t>::output_debug_string(const wchar_t *text)

That's really all you need, but as a convenience I also provide a class derived from basic_ostream that connects the output stream to the basic_debugbuf just created.

In order to work just like cout, you should then create a global object of type dostream or wdostream and use that to output to.

template<class CharT, class TraitsT = std::char_traits<CharT> >
class basic_dostream : 
    public std::basic_ostream<CharT, TraitsT>

    basic_dostream() : std::basic_ostream<CharT, TraitsT>
                (new basic_debugbuf<CharT, TraitsT>()) {}
        delete rdbuf(); 

typedef basic_dostream<char>    dostream;
typedef basic_dostream<wchar_t> wdostream;


  • 18-apr-2001 - Original version
  • 23-nov-2001 - Updated to use a stringbuf as suggested by Jim Barry.
    Also fixed the remaining HTML markup errors that made the code un-compileable


This article, along with any associated source code and files, is licensed under A Public Domain dedication


About the Author

Sven Axelsson
Web Developer
Sweden Sweden
No Biography provided

You may also be interested in...


Comments and Discussions

GeneralRe: Usage Pin
Anonymous12-Feb-02 17:45
memberAnonymous12-Feb-02 17:45 
GeneralBetter to use basic_stringbuf Pin
Jim Barry22-Apr-01 5:12
memberJim Barry22-Apr-01 5:12 
GeneralA small bug Pin
Sven Axelsson18-Apr-01 2:31
memberSven Axelsson18-Apr-01 2:31 
Generalstlport Compatability Pin
Patrick DellEra18-Apr-01 1:16
memberPatrick DellEra18-Apr-01 1:16 
GeneralRe: stlport Compatability Pin
Sven Axelsson18-Apr-01 2:27
memberSven Axelsson18-Apr-01 2:27 
QuestionCan't Compile?? Pin
Patrick DellEra17-Apr-01 11:40
memberPatrick DellEra17-Apr-01 11:40 
AnswerRe: Can't Compile?? Pin
Sven Axelsson17-Apr-01 12:04
memberSven Axelsson17-Apr-01 12:04 
GeneralRe: Can't Compile?? Pin
Patrick DellEra17-Apr-01 13:23
memberPatrick DellEra17-Apr-01 13:23 
Excellent. I was afraid I was going crazier. Big Grin | :-D
GeneralOutputDebugString Pin
Simon C. Smith16-Apr-01 23:31
memberSimon C. Smith16-Apr-01 23:31 
GeneralRe: OutputDebugString Pin
Sven Axelsson17-Apr-01 1:19
memberSven Axelsson17-Apr-01 1:19 
GeneralRe: OutputDebugString Pin
simon smith17-Apr-01 1:22
membersimon smith17-Apr-01 1:22 
GeneralYou may also want to check out this Pin
Daniel Lohmann13-Apr-01 4:29
memberDaniel Lohmann13-Apr-01 4:29 
GeneralBug Pin
Arnaud Brejeon12-Apr-01 22:41
memberArnaud Brejeon12-Apr-01 22:41 
GeneralRe: Bug Pin
Sven Axelsson13-Apr-01 6:40
memberSven Axelsson13-Apr-01 6:40 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

Permalink | Advertise | Privacy | Terms of Use | Mobile
Web03 | 2.8.180221.1 | Last Updated 25 Nov 2001
Article Copyright 2001 by Sven Axelsson
Everything else Copyright © CodeProject, 1999-2018
Layout: fixed | fluid