Q: I want to read all the error messages that GCC throws at me, but
there are so many that I can't keep up. How can I redirect them to a
Q: When I add
-v to the GCC command line, how can I put all the
voluminous output into a file, so I don't miss anything when reporting a
Q: I have this nifty graphics program which bombs from time to time,
but the registers and traceback info are hidden by the graphics display.
How can I see it?
A: Error messages are usually written to
stderr, and stock
COMMAND.COM cannot redirect it. There are several alternatives
to do that:
COMMAND.COM, such as
bash, which knows how to redirect standard error stream to a file. 4DOS is shareware and can be found on SimTel.NET, while
bashis available from the
v2gnudirectory of DJGPP archives on SimTel.NET.
SCRIPT, which is similar to its Unix namesake. It has an advantage of saving everything which goes to screen and showing it on the screen at the same time. You can find SCRIPT on SimTel.NET.
REDIRprogram which comes with DJGPP. It also redirects standard output and/or standard error to a file, but you don't get a chance to look at the output while the program runs. Here's how to run GCC with
redir -o gcc.log -eo gcc -v ...
(put the rest of the GCC command line instead of the dots). The
messages printed by GCC will be written to the file
Windows/NT has its own program named
redir.exe, so make sure the
bin subdirectory is listed in the
before the NT directories.