ID Number: Q57870
1.x 2.x 3.00 3.10 3.11 3.14 | 2.x 3.00 3.10 3.11 3.12 3.50
MS-DOS | OS/2
Summary:
In versions of CodeView earlier than version 2.3, it is not possible
to redirect the input or output of the program being debugged. For
example, a "filter" program that takes input from a file specified by
the input redirection operator ("<") is hindered by this limitation
under pre-2.3 CodeView because there is no way to specify that you
want the redirection to apply to the application rather than to
CodeView itself.
More Information:
In CodeView (CV) versions 2.3 and later, redirection on the command
line following the program name is directed to the program being
debugged. For example, invoking CodeView 2.3 or later with the
following command line causes all input to the program TEST.EXE to be
read from the file TEST.DAT:
CV test < test.dat
Redirecting I/O to CodeView is useful for involved debugging sessions
where many CodeView dialog commands can be put into a separate text
file that is automatically read by CodeView during debugging. For
instance, this method will allow a complicated debugging scenario to
be accurately repeated any number of times. Prior to CV and CVP 2.3,
this was the only type of redirection supported while debugging.
Starting with CodeView 2.3, you can redirect I/O to both the
application being debugged and to CodeView. The CodeView redirection
is done with the /C command-line option, or from within CV with the
redirection dialog commands ("<" and ">"). Because the /C switch
allows you to specify CV dialog commands on the command line, you can
specify the redirection at this point. For example, the following
command line brings up CodeView with TEST.EXE, as in the example above
(with the TEST.EXE input coming from TEST.DAT); however, CodeView also
reads the debugging instructions to perform from the file CV.DAT.
CV "/C<cv.dat" test < test.dat
Additional reference words: 1.0 1.00 1.1 1.10 1.11 2.0 2.00 2.1 2.10
2.2 2.20 2.30 2.30 2.35 3.0 3.00 3.1 3.10 3.11 3.12 3.14 3.5 3.50