Skip to content
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

Send crash log/dump to remote url when app crash/error #92

Open
AndryBray opened this issue Dec 3, 2013 · 2 comments
Open

Send crash log/dump to remote url when app crash/error #92

AndryBray opened this issue Dec 3, 2013 · 2 comments

Comments

@AndryBray
Copy link

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:

  1. user opens the app
  2. at certain point the app will crash and generate the minidump file
  3. the app will send (if user confirm - for privacy reason) the log/dump to our remote url with one HTTP POST request

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!

@AndryBray
Copy link
Author

My thought about that:

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.

@trevorlinton
Copy link
Member

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants