Before upgrading to 4.20, each crash opened a crash report into the crash reporter with all the callstack. Debugging a crash was easy. But since I upgraded to 4.20, after crashs, crash reporter doesn’t appear and I just get last call before crash into the logs. I have debug symbols installed.
Thanks for the precision.
But it remains a problem, how can I see the callstack ? Just last call is in the logs and it’s always engine’s functions so not very useful…
I have Debugs symbols installed.
We’ve recently made a switch to a new bug reporting method using a more structured form. Please visit the link below for more details and report the issue using the new Bug Submission Form. Feel free to continue to use this thread for community discussion around the issue.
We’ve also seen with our project ‘Shipping build’ crash in 4.20 and not show the crash reporter (and yes it is set to be included on the build settings). We are still on 4.16 so we were able to fix it but would not have been able to easily otherwise.
What about working with in house QA on project code crashes? Is there a tool/workflow to that end or do we need to develop our own logging/callstack-dumping code?
What about working with in house QA on project code crashes? Is there a tool/workflow to that end or do we need to develop our own logging/callstack-dumping code?