Mail Archives: djgpp/1994/08/24/21:43:53
How does one capture the error messages GCC spits out if it encounters
errors? I've had programs with only 1 to 2 errors cause several
screenfulls of error messages, and because they scroll off the screen so
fast, I don't have a chance to see the first ones which are the most
important ones. I've tried redirecting or piping, but that doesn't
work. The only thing that has worked so far is to hit the turbo button
to slow things down, and then recompile and press CTRL-S when the
messages start to appear. There u^
- Raw text -