Debugging Console Apps Using Redirection (102351)
The information in this article applies to:
- Microsoft Platform Software Development Kit (SDK) 1.0, when used with:
- Microsoft Windows NT Server 3.1
- Microsoft Windows NT Server 3.5
- Microsoft Windows NT Server 3.51
- Microsoft Windows NT Server 4.0
- Microsoft Windows NT Workstation 3.1
- Microsoft Windows NT Workstation 3.5
- Microsoft Windows NT Workstation 3.51
- Microsoft Windows NT Workstation 4.0
This article was previously published under Q102351 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:
However, the following syntax will not work when attempting to debug
this application using WinDbg with STDIN redirected:
To debug the application as desired, use
windbg cmd /c "app < input.txt"
MORE INFORMATION
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.
| Modification Type: | Minor | Last Reviewed: | 7/11/2005 |
|---|
| Keywords: | KB102351 |
|---|
|