We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

We can't necessarily write to the directory where the .exe is located (say, it's a Vista system with a game installed by the admin).

If this gets changed, perhaps we should write this to somewhere under "My Documents" or whatever it's called now (or have a way to just disable it for people that don't care about the text files)?

--ryan.

(In reply to comment #1)
> We can't necessarily write to the directory where the .exe is located (say,
> it's a Vista system with a game installed by the admin).
> If this gets changed, perhaps we should write this to somewhere under "My
> Documents" or whatever it's called now (or have a way to just disable it for
> people that don't care about the text files)?
> --ryan.

That's true. An equiavalent of $HOME should be more appropriate on systems
that handle user privileges.

Why I consider current directory as bad location ? Imagine that user associates
some mimetype (or file extension) to a program which uses SDL. Then double-click opened file will result in stdout.txt in it's directory.

Tagging this bug with "target-1.2.14" so we can try to resolve it for SDL 1.2.14.

Please note that we may choose to resolve it as WONTFIX. This tag is largely so we have a comprehensive wishlist of bugs to examine for 1.2.14 (and so we can close bugs that we'll never fix, rather than have them live forever in Bugzilla).

--ryan.

SDL 1.3 no longer generates these files.  Since they're intended for debugging only, I'm going to punt for SDL 1.2.