This bug report was migrated from our old Bugzilla tracker.

These attachments are available in the static archive:

• printf usage in test code (test-printfs.txt, text/plain, 2013-08-13 22:37:24 +0000, 33966 bytes)

Reported in version: 2.0.0
Reported for operating system, platform: Windows 7, x86

Comments on the original bug report:

On 2013-08-13 22:37:24 +0000, Andreas Schiffler wrote:

Created attachment 1285
printf usage in test code

On 8/13/2013 10:15 AM, George Brink wrote:

Second problem.
All tests are compiled with -mwindows key, even those which are supposed to be a console applications. So no stdout/stderr is available and all printf()/frprintf(stderr) are going to nul.
Manual recompilation without -mwindows key solves the problem.

All the printf's should be converted to SDL_Log or SDLTest_Log calls which will go through the platform specific SDL output routine which will attach the console streams on windows if available.

Changes needed are:
$ grep printf *.[ch] | grep -v SDL_snprintf | grep -v SDL_vsnprintf | grep -v "Binary file" >test-printfs.txt

On 2013-08-14 02:39:48 +0000, Sam Lantinga wrote:

Agreed!

On 2013-08-14 12:01:04 +0000, Andreas Schiffler wrote:

Working on it (nice and easy project).

On 2013-08-15 02:32:51 +0000, Andreas Schiffler wrote:

Fixed with:
http://hg.libsdl.org/SDL/rev/9406b7dd2f2d