You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I suppose that we can't handle a crash situation at run-time, so each time the user will open the app, we look for any new/recent file (maybe using a localstorage to keep track of sent dumps) inside "~/Library/Breakpad/appname" (MacOS example) and send to server the dumps still not tracked in the localstorage, than track them.
Of course it could be better if there is a lower level script to do it at runtime.
@AndryBray Interesting, it should be possible with the recent addition of breakpad support. I'll have to look into if there's any normal "conventions" built into the OS for handling delivering debug information, if its something custom perhaps it would prompt the user then post the dumb to a url provided when compiling.
Hi @trevorlinton
what do you think about a new feature to let us define a "dump handler remote url" ?
It could be something like that:
The 3d point could be even at the next opening (not necessarily when crash).
I'd like to know your though about it, thank you!
The text was updated successfully, but these errors were encountered: