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

Standardized way of publishing debug files #70

Open
hrueger opened this issue Sep 29, 2022 · 0 comments
Open

Standardized way of publishing debug files #70

hrueger opened this issue Sep 29, 2022 · 0 comments

Comments

@hrueger
Copy link

hrueger commented Sep 29, 2022

Hi,
I'm currently fighting a few crashes in my electron app related to native modules. Since the stack traces generated by minidump are not very helpful without the debug files generated at build time of the modules, we're having trouble figuring out what the problem is, for example here and here.

If the build pipeline could download the debug files generated by prebuildify (for example .pdb on Windows) and upload it to the Crash Reporting Service (in my case Sentry), it would allow for much easier debugging.

How could this be achieved in a standardized way, so that people don't have to write a separate download script for the debug files of each package?

I don't think it's a good idea to include those files in the publish tarball (for npm for example), because they can be quite big and are (as far as I know) not needed in the application itself but rather for the crash reporting service on the serverside.

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

No branches or pull requests

1 participant