Debugging Console Apps Using Redirection

Article translations Article translations
Article ID: 102351 - View products that this article applies to.
This article was previously published under Q102351
Expand all | Collapse all


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.


Article ID: 102351 - Last Review: July 11, 2005 - Revision: 2.2
  • Microsoft Platform Software Development Kit-January 2000 Edition, when used with:
    • Microsoft Windows NT Advanced Server 3.1
    • Microsoft Windows NT Server 3.5
    • Microsoft Windows NT Server 3.51
    • Microsoft Windows NT Server 4.0 Standard Edition
    • Microsoft Windows NT Workstation 3.1
    • Microsoft Windows NT Workstation 3.5
    • Microsoft Windows NT Workstation 3.51
    • Microsoft Windows NT Workstation 4.0 Developer Edition

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from