debug() in windows (3.1 rc2)

[Duha]

Hi,

I try to launch game from cmd (windows console) but it runs in separate process (like launching in linux terminal with &)
How can I get debug prints?

3.1 rc2
Win7-64

[NoQ]

Hmm. Do you have anything interesting in logs/WZlog-*.txt?

[Duha]

Hmm. Do you have anything interesting in logs/WZlog-*.txt?

No, just standard logs with "info" entries.

[vexed]

All debug() statements will show in the log, if and only if it is turned on.
Info, Fatal, and something else is on by default, the rest you need to run the game like --debug=all (for everything), --debug=3d (for debug calls that use LOG_3D) and so on.

If you want to reroute to the console, then I think you can use 1>* 2>* or something along those lines...

[NoQ]

The talk is about the JS debug() function.

[vexed]

The talk is about the JS debug() function.

Shouldn't post late at night.

[NoQ]

js_debug calls qWarning to print the text.

[Duha]

js_debug calls qWarning to print the text.

void qWarning ( const char * msg, ... )
Calls the message handler with the warning message msg. If no message handler has been installed, the message is printed to stderr. Under Windows, the message is sent to the debugger. This function does nothing if QT_NO_WARNING_OUTPUT was defined during compilation; it exits if the environment variable QT_FATAL_WARNINGS is defined.

[Duha]

js_debug calls qWarning to print the text.

void qWarning ( const char * msg, ... )
Calls the message handler with the warning message msg. If no message handler has been installed, the message is printed to stderr. Under Windows, the message is sent to the debugger. This function does nothing if QT_NO_WARNING_OUTPUT was defined during compilation; it exits if the environment variable QT_FATAL_WARNINGS is defined.

I solve it via external tool:
viewtopic.php?f=35&t=10080

[Per]

So should I change javascript debug() to use the C debug() as a quick fix? Then it will show up in the log files, at least.

[Duha]

So should I change javascript debug() to use the C debug() as a quick fix? Then it will show up in the log files, at least.

If you plan solid fix later, don`t spend you time for quick fix. I have work around this, it is not trouble for me anymore. But changes can break someone workflow.

[aubergine]

Why not just have it do both - what it currently does and also put the debug in to the log file as well?

[Per]

Why not just have it do both - what it currently does and also put the debug in to the log file as well?

Because on Linux that would print double of every debug line...

[aubergine]

Could it do just one if it detects that it's running on linux? (I assume there is some way to detect which platform the game is being run on or compiled for?)

[aubergine]

Where does debug output currently go on Mac OS X? It's not in the logs (as far as I can tell) and not sure how to see the stderr for an app launched via an icon in apps folder :s