Debugging Console Apps Using Redirection

View products that this article applies to.

This article was previously published under Q102351

Expand all | Collapse all

SUMMARY

To redirect the standard input (STDIN) for a console application named APP.EXE from a file named INPUT.TXT, the following syntax is used:

app < input.txt

However, the following syntax will not work when attempting to debug this application using WinDbg with STDIN redirected:

windbg app < input.txt

To debug the application as desired, use

windbg cmd /c "app < input.txt"

This will allow WinDbg to debug whatever goes on in the cmd window. A dialog box will be displayed that says "No symbolic Info for Debuggee." This message refers to CMD.EXE; dismiss this dialog box. When the child process (APP.EXE) is started, the command window will read "Stopped at program entry point." To continue, type "g" at the command window. Note that APP.EXE will begin executing, then you can open the source file and set breakpoints.

This technique is also useful when debugging an application that behaves differently when run with a debugger than it does when it is run in the command window.