[SDL] Re: I/O problem (stdio and stderr redirection to txt files)

Rainer Deyke rainerd at eldwood.com
Sat Mar 19 00:31:58 PST 2005

Donny Viszneki wrote:
> In this thread, the necessary severity for an
> SDL application to be unable to communicate with the user
> is generally going to be a segmentation fault, or corrupt
> and/or missing resource files. Why is this where the
> distinction is drawn? Because if you can find your
> resources, and you haven't crashed, then you are still
> able to report the error to the user.

SDL_SetVideoMode failing (due to anything from requesting an unsupported
resolution to lack of OS resources) can also be considered a critical error
in some contexts.

> Typically, your X
> session will send the non-graphical of a graphical
> application to a log, the system console (or another
> similar "console" file) or sometimes nowhere. However,
> most Unix users know this. I'm sorry you did not. The
> fact that you didn't is probably a good indication that I
> am better than you to say what the typical Unix user is
> likely to know. (Read: most Unix users are not newbs, and
> know how to retrieve the non-graphical output of their
> graphical applications.)

I also did not know this, and I've used Unix systems for years.

Rainer Deyke - rainerd at eldwood.com - http://eldwood.com

More information about the SDL mailing list