Please refer to their respective documentation on how to build and integrate them. These are most notably Crashpad and Breakpad. The SDK already takes care of this difference, so there is no need to manually disable enableNative.įor custom child processes, especially ones not written in JavaScript, you need to integrate a library that can generate Minidumps. To receive crash reports for child processes, you need to make sure the crash reporter is activated by either the SDK or manually (see below).Īn exception to this is macOS, where the crash reporter only needs to be started in the main process and watches all its child processes. The SDK relies on the Electron CrashReporter to generate the crash dumps. See Debug Information Files for a detailed description of how to If your application contains custom native extensions or you wish to symbolicateĬrashes from a spawned child process, upload their debug information manuallyĭuring your build or release process. You can add more symbol servers for the platforms youĪre deploying to, depending on your needs. Go to Project Settings > Debug Files and choose Electron from the list ofīuiltin Repositories. (sometimes also referred to as Debug Symbols or just Symbols).įirst, make sure that the Electron Symbol Server is enabled for your project. Symbolicated stack traces, you need to upload Debug Information Files To allow Sentry to fully process native crashes and provide you with Once processed, they are removed immediately and all sensitive information is stripped from the resulting issues. Sentry does not store these memory dumps. As such, they might contain sensitive information on the target system, such as environment variables, local path names or maybe even in-memory representations of input fields including passwords. Minidumps are memory dumps of the process at the moment it crashes. In this case, native crash handling will be disabled.
#GODOCS SENTRY MAC#
All event meta data including user information and breadcrumbs are included in these uploads.ĭue to restrictions of macOS app sandboxing, native crashes cannot be collected in Mac App Store builds. To do so, the SDK needs to upload those files once the application restarts (or immediately for renderer crashes). Sentry can process Minidumps created when the Electron process or one of its renderers crashes. If you upload source maps in addition to your minified files that data becomes available in Sentry. This feature will be added in a future SDK update. The release and environment can also be specified in the environment variables SENTRYRELEASE and SENTRYENVIRONMENT respectively. If you specify the SENTRYDSN environment variable, this will be done automatically for you. Also, crash reports from sub processes will not be reported automatically on all platforms. To use raven-go, you’ll need to import the raven package, then initialize your DSN globally. However, crashes will still be reported to Sentry if they happen in a process where the SDK has been configured.
#GODOCS SENTRY CODE#
It is currently not possible to send events from native code (such as a C++ extension).
0 kommentar(er)
