Date: Sun, 20 Aug 1995 13:00:16 +0300 (IDT) From: Eli Zaretskii To: "Ed. Mueller" Cc: djgpp AT sun DOT soe DOT clarkson DOT edu Subject: Re: FAQ answers I can't find On Mon, 14 Aug 1995, Ed. Mueller wrote: > I can't find these answers in the 1.02 FAQ (not to say they aren't there): They are; read below. > 1. How can I create a file containing the errors generated by a compile? > Redirecting the output using ">" on my DOS 6.2 machine doesn't work > (though it does on Unix). 6.13 Q: I want to read all the error messages that gcc throws on me, but they are so many that I can't keep up. How can I redirect them to a file? 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 problem? Q: I have this nifty graphics program which bombs from time to time, but the registers and traceback info is hidden by the graphics display. How can I see it? A: There are several alternatives: 1) You can put ``2r1'' into your GO32 environment variable, which will redirect stderr to stdout, and redirect stdout to a file by appending ``> file''to your command line. See question 5.1 above. 2) You can use a shell smarter then COMMAND.COM, such as 4DOS, which knows how to redirect standard error stream to a file. 4DOS is shareware and can be found, e.g., on SimTel mirrors. 3) You can add ``core file'' to your GO32 environment variable, to have your traceback written to the named file. This only works for the exception traceback redirection (useful when running graphics applications). 4) You can run your program under any one of the programs which save the output of programs they spawn in a file. I suggest using a program called 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. SCRIPT can be found on SimTel mirrors as SCRIPT11.ZIP (e.g., oak.oakland.edu:/SimTel/msdos/screen/script11.zip). > 3. Although I've installed the four maint. updates to 1.12, my go32 is still > at version maint3. What do I need to do to get maint4 of go32? 3.10 Q: I've installed the 1.12m4 maintenance release, but go32 still displays its version as 1.12maint3. Huh? A: Usually, go32 revision gets updated for each new maintenance release, but sometimes it won't. When in doubt, look in the djXXXmN.zip to see if there is a new go32.exe there, or ask on the newsgroup or the mailing list (see question 20.2).