I could not understand what do you exactly mean by the debug output.
What i understand by the debug output is that you want to see the
sequence of instructions called, runtime process list, thread blocks,
loaded driver list, memory usage information, and so on.
Attach the process spoolsv.exe in the WinDbg and open the .cpp files
(you want to put breakpoint in) you want to debug.
Another alternative method is to simply open the notpad.exe in WinDbg
and open the files you want to debug.
Put a message box at the point where you want to put the breakpoint
(since breakpoints could not be put until the dll gets loaded) and then
run the process. Fire a print command. When the messagebox will appear
that mean the dll you want to debug is loaded and now you can pause the
Windbg and put the breakpoints at the desired positions.
Saurabh Aggrawal