ED/EDMarketConnector
1
0
Fork 0
mirror of https://github.com/EDCD/EDMarketConnector.git synced 2025-04-22 11:50:28 +03:00
Code Issues Projects Releases Wiki Activity

Troubleshooting: Plain log file is only on Windows now. 

* Only Windows, running from .exe, has the redirect of stdout/err.
* For any "Running from source" the user will need to capture the output
  themselves.
Athanasius 2021-03-22 08:59:00 +00:00
parent 9a504263f2
commit 97e14d5392
1 changed files with 19 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
Troubleshooting.md

@ -705,14 +705,24 @@ reports as well.
<!-- vim-markdown-toc -->
## Plain Log File
Prior to EDMC 4.1.0 the only logfile is re-created on each run of the program.
As such you will need to re-create the issue and then make a copy of the file:
As well as the [Debug log file](#debug-log-files) there is also the actual
console output of the program. This can contain a little extra output not
found in the Debug log file, such as exceptions and tracebacks.
**It is vital you attach *this* file/output to bug reports as well.**
* Windows: `%TEMP%\EDMarketConnector.log`
* Mac: `$TMPDIR/EDMarketConnector.log`
* Linux: `$TMPDIR/EDMarketConnector.log`
When running from the provided Windows
installer this is redirected to:
This file contains redirected "standard and error output", i.e. all console
output of the program. As such it might contain output not present in the
[debug log files](#debug-log-files) and it is vital you attach *this* file
to bug reports as well.
%TEMP%\EDMarketConnector.log
With the old (up to 3.43) macOS installer this is found in:
${TMPDIR}/EDMarketConnector.log
In all cases of [Running from source](Running-from-source.md) you will need to
capture the output of `EDMarketConnector.py`, e.g. on Linux or macOS:
EDMarketConnector.py 2>&1 | tee "${TMPDIR}/EDMarketConnector.log"
You can make that `... | tee -a ...` if you're OK with this log file growing
until you delete or truncate it yourself.