Inconsistance between Log & Crash Report
since 1 or 2 versions, we have a discrepancies between what's in the log file and what is avalaible in the CrashReport data. Log file is not as detailled as the CrashReport data.
Repro - Launcher binaries -
In the logs, we don't have anymore the stack trace and we don't have the error message.
If is intended, could you please share the reasons of this change and eventually add an option to allow or not Detailled Crash logs?
asked Oct 26 '15 at 10:08 AM in Bug Reports
This is by design. Generating call stacks at run-time is time and memory consuming and it is disabled by default. Crash report client is the tool for that, but if you want to enable run-time call stack generation, add this parameter to the command line
Follow this question
Once you sign in you will be able to subscribe for any updates here