Fix logging of error messages on Windows
Bug #1792521 reported by
GunChleoc
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
widelands |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
STDERR gets lost in windows, error messages are neither printed to console nor to the stdout.txt.
Follow-up from https:/
summary: |
- Fix logging of error messges on WIndows + Fix logging of error messages on Windows |
To post a comment you must log in.
Hmm, there is another aspect of sending this to the Homedir: klaus\. widelands\ stdout. txt
> Log output will be written to: C:\Users\
I wanted to debug smugglers and stated two widelands instances.
To make one write to some other File I tried to use:
> ./widelands.exe --homedir= /mnt/d/ develop/ wldev/3772- 1/home/
# From Linux Subystem on Win 10
> D:\develop\ wldev\3772- 1>widelands. exe --homedir= D:\develop\ wldev\3772- 1\home
# From Windows cmd
but both give me an assertion
File: src/base/log.cc, Line 151
Expression: logger != nullptr
So how can I check the logs of both instances now?