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.

Sign up for GitHub

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

Jump to bottom

Block until flush previous crashes #575

Closed
Renat060888 opened this issue Jul 13, 2021 · 2 comments
Closed

Block until flush previous crashes #575

Renat060888 opened this issue Jul 13, 2021 · 2 comments
Labels
enhancement New feature or request

Comments

@Renat060888
Copy link

Description

Hello everyone!

I noticed that if an error is found immediately after sentry initialization, it does not have time to send a dump to the server. Can I somehow block execution (e.g. sentry_inti( ..., block_until_flush )) before the data (crash on previous launch) is unploaded? ( sorry for my eng :)

I'm testing simple fake SEGFAULT just after sentry init.

When does the problem happen
During run-time

Environment
OS: Linux 4.19.0
Compiler: clang-12
Sentry: native 0.4.9 breakpad
CMake: 3.20.1
@Swatinem
Copy link
Member

We have a method to explicitly flush queued events in other SDKs. Implementing this for native would give you an explicit sentry_flush(timeout) or similar method, so you can call that directly and decide on a suitable timeout.

@Swatinem Swatinem added enhancement New feature or request and removed Status: Untriaged labels Jul 16, 2021
@Swatinem
Copy link
Member

Landed in #670, we will be tagging a new release soon-ish.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Swatinem @Renat060888