Microsoft KB Archive/102351: Difference between revisions
(stage2) |
m (Text replacement - "<" to "<") |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 26: | Line 26: | ||
To redirect the standard input (STDIN) for a console application named APP.EXE from a file named INPUT.TXT, the following syntax is used: | To redirect the standard input (STDIN) for a console application named APP.EXE from a file named INPUT.TXT, the following syntax is used: | ||
<blockquote>app | <blockquote>app < input.txt</blockquote> | ||
However, the following syntax will not work when attempting to debug this application using WinDbg with STDIN redirected: | However, the following syntax will not work when attempting to debug this application using WinDbg with STDIN redirected: | ||
<blockquote>windbg app | <blockquote>windbg app < input.txt</blockquote> | ||
To debug the application as desired, use | To debug the application as desired, use | ||
<blockquote>windbg cmd /c | <blockquote>windbg cmd /c "app < input.txt"</blockquote> | ||
<br /> | <br /> | ||
| Line 38: | Line 38: | ||
== MORE INFORMATION == | == MORE INFORMATION == | ||
This will allow WinDbg to debug whatever goes on in the cmd window. A dialog box will be displayed that says | 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.<br /> | ||
<br /> | <br /> | ||
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. | 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. | ||
Latest revision as of 10:06, 20 July 2020
Debugging Console Apps Using Redirection |
Q102351
The information in this article applies to:
- Microsoft Win32 Software Development Kit (SDK), on platform(s):
- Microsoft Windows NT Server versions 3.1, 3.5, 3.51, 4.0
- Microsoft Windows NT Workstation versions 3.1, 3.5, 3.51, 4.0
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"
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.
Additional query words: 3.10 3.50 4.00 95
Keywords : kbSDKWin32 kbDSupport
Issue type :
Technology : kbWin32SDKSearch kbAudDeveloper kbSDKSearch kbWin32sSearch
Last Reviewed: October 27, 2000 |
