-
-
Notifications
You must be signed in to change notification settings - Fork 313
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
Create a crash 'report' #3308
Comments
Here it is #391 It's embarassing I lost track of time 😅 |
Ouch. So it was an issue indeed XD The first version could just work on a single system (Linux or Windows) and just write the crash report file in a known place. |
@rodolforg Track this issue and close the older one. I can't resume currently with my priorities set on my ongoing studies.
Those are well established solid steps. One by one is much better than getting overwhelmed with tackling multiple objectives at once. I tried to do it that way in the old linked issue and see where I am now 😅 😭 |
As we all know, sadly Synfig Studio has some (random?) crashes around.
On Windows, specifically, we have more, maybe due to GTK port or version we embed. Some (a lot) errors that happen on Windows releases don't happen on Linux. So what about we do provide a way to Synfig user send us a crash report file?
I know @Keyikedalube was studying about it a while ago, but I couldn't find where he stated it :P
So here are some promising links I just found:
https://github.com/jrfonseca/drmingw -> we can embed it on our winmain... : https://github.com/jrfonseca/drmingw#exchndl
Here is an 'alternative way':
https://stackoverflow.com/questions/51658214/detecting-a-process-crash-in-c-win32
And here, if it works, it can be used to show a window with a "send report", maybe :P
https://crashrpt.sourceforge.net/
I know that, in all cases, we need to ship the debug symbols somehow. How much would it cost (performance and storage)?
https://stackoverflow.com/a/15395871
https://stackoverflow.com/questions/5705650/stackwalk64-on-windows-get-symbol-name
The text was updated successfully, but these errors were encountered: