sentry-native: Provide Breakpad and inproc backends for Windows

Hi!

My remaining problem now is that I’m not seeing any crashes reported in the Browser.

NB I’m provoking a crash in response to a menu item within the app, which calls this code:

      // Force crash report for sentry.io
      int* crashPtr = nullptr;
      *std::launder(crashPtr) = 0;

The app does indeed crash as expected, but for the avoidance of doubt, I see no report about this on the sentry.io website.

I’ve enabled this line as requested: sentry_options_set_debug(options, 1);

NB I don’t know if this is relevant, but I’ve noticed that, whether or not I crash the app, or have the sentry_options_set_debug call, I’m no longer seeing anything reported on the sentry.io site sent from sentry_capture_event(…) … unless I modify the “message” parameter in the call below. In otherwords, only the first call is reported on the site. Subsequent calls aren’t reported on the site.

sentry_capture_event(sentry_value_new_message_event( /* level / SENTRY_LEVEL_INFO, / logger / “custom”, / message */ “Prepare to crash…” ));

Hopefully you see something useful on the server! 😃

Best wishes,

Pete

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 16 (7 by maintainers)

Most upvoted comments

Hi @Swatinem,

The Windows 10 Store C++ apps are configured in a very specific way. I’ll try to give you the necessary background info in this post.

The style of C++ app in question, are Windows apps using “Windows Application Packaging Projects” to deliver them through the Windows Store.

See https://docs.microsoft.com/en-us/windows/uwp/porting/desktop-to-uwp-packaging-dot-net for info on how to do this. It is certainly pretty easy to configure a C++ app for deployment through the Windows 10 store using this approach.

So, assuming you have a simple test C++ app for Windows, it is easy enough to wrap-up like this, and see what the options might be for Sentry native.

Hoping this info all helps.

Best wishes,

Pete

sseyod on Mar 23, 2020