[squeak-dev] Lost stdOut and stdErr handles?
David T. Lewis
lewis at mail.msen.com
Wed Apr 3 01:05:19 UTC 2013
On Tue, Apr 02, 2013 at 07:53:06PM -0500, Chris Muller wrote:
> I have an image that seems to no longer be able to write to stdout or
> stderr. It most definitely was doing that at one time, but now none of the
> redirection works, however I am seeing actual files called "stdout" and
> "stderr" in the image directory with output from all of my running images
> written on top of each other -- unreadable.
>
> Just to make sure it wasn't something in my OS, I tried another image and
> writing to stdout works fine.
>
> I'd like to stay in this image if I can, is there some way to "reset"
> things back to normal? I poked around in the related FileStream methods
> but didn't see anything quick and obvious..
You can probably just nil out the Stdout Stderr Stdin class variables in
FileStream, and I expect that everything will return to normal once reinitialized.
And of course you can always use the old standby:
OSProcess thisOSProcess stdOut
OSProcess thisOSProcess stdErr
OSProcess thisOSProcess stdIn
Dave
More information about the Squeak-dev
mailing list
|