-
-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose backtrace for blenderplayer. #739
Comments
panzergame
added a commit
that referenced
this issue
Oct 19, 2018
Blenderplayer now supports backtrace write into text file of the name of the current loaded file or default "blender". This file contain the backtrace constructed during a SIGSEGV. Useful for bug report. GPG_ghost.cpp mimic creator part by setting up a signal function sigHandleCrash (or windowsExceptionHandler for windows which call sigHandleCrash at the end) calling sigHandleCrashBacktrace in responsible of writing the file using BLI_system_backtrace. Fix issue: #739.
panzergame
added a commit
that referenced
this issue
Nov 30, 2018
Blenderplayer now supports backtrace write into text file of the name of the current loaded file or default "blender". This file contain the backtrace constructed during a SIGSEGV. Useful for bug report. GPG_ghost.cpp mimic creator part by setting up a signal function sigHandleCrash (or windowsExceptionHandler for windows which call sigHandleCrash at the end) calling sigHandleCrashBacktrace in responsible of writing the file using BLI_system_backtrace. Fix issue: #739.
youle31
pushed a commit
that referenced
this issue
May 26, 2019
Blenderplayer now supports backtrace write into text file of the name of the current loaded file or default "blender". This file contain the backtrace constructed during a SIGSEGV. Useful for bug report. GPG_ghost.cpp mimic creator part by setting up a signal function sigHandleCrash (or windowsExceptionHandler for windows which call sigHandleCrash at the end) calling sigHandleCrashBacktrace in responsible of writing the file using BLI_system_backtrace. Fix issue: #739.
Closing as this one was implemented |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently no backtrace are exposed to the user when something wrong happened.
It should be interesting to print in console a backtrace and a link to the github issues to report a bug.
The text was updated successfully, but these errors were encountered: