*BSD News Article 3922


Return to BSD News archive

Path: sserve!manuel!munnari.oz.au!network.ucsd.edu!usc!zaphod.mps.ohio-state.edu!rpi!newsserver.pixel.kodak.com!laidbak!tellab5!vpnet!serveme!tallboy!news
From: George Jetson <pynq@midway.uchicago.edu>
Newsgroups: comp.unix.bsd
Subject: Report small bug (?) in GO32
Message-ID: <9208172142.AA18831@midway.uchicago.edu>
Date: Mon, 17 Aug 92 16:42:57 CDT
Sender: news@tallboy.chi.il.us
Lines: 13

I did something like:

	go32 foo bar bletch > outfile

and it exited quickly back to the the DOS prompt (it should have run for
awhile).  Turned out that I had forgotten to set GCCTMP, and it could
not open the swap file.  However, the msg to that effect ended up in
OUTFILE.  I suggest that GO32 error msgs go to stderr, not stdout.

Actually, a case can be made that they should just be blasted
to the terminal (something like to "CON" [In Unixese, /dev/tty]),
since at this point, your program has not even run (it might want
to have exclusive control over the contents of the stderr stream)