Debug C apps and prevent crashes across your entire stack with Sentry. Resolve issues with an C monitoring workflow that actually improves the debugging process.
The Native SDK supports Windows, macOS, Linux, and Android. CMake
can be used like this (on macOS):
# configure the cmake build into the `build` directory, with crashpad (on macOS) cmake -B build -D SENTRY_BACKEND=crashpad --config RelWithDebInfo # build the project cmake --build build --config RelWithDebInfo --parallel # install the resulting artifacts into a specific prefix cmake --install build --prefix install # which will result in the following (on macOS): exa --tree install
Import and initialize the Sentry SDK early in your application setup:
#include <sentry.h> int main(void) { sentry_options_t *options = sentry_options_new(); sentry_options_set_dsn(options, "https://[email protected]/5202964"); sentry_options_set_release(options, "[email protected]"); sentry_init(options); /* ... */ // make sure everything flushes sentry_shutdown(); }
Check our documentation for the latest instructions.
See all platformsSee details like filename and line numbers so you never have to guess with C errors. Filter and group C exceptions intuitively to eliminate noise. Monitor errors at scale without impacting throughput in production.
Use issue graphs to understand the frequency, scope, and impact ofC errors so you can prioritize what needs to be fixed. Get alerts via email, SMS, or chat when bugs make it into production without disrupting your development workflow.
Get real-time insights immediately. Setup takes just a few minutes and typically requires only two lines of code. If you need help, we’ve built a full documentation library to handle any debugging scenario.
Understand the context that contributed to errors with tags and relevant information about your software, environment, and users.
You can also submit optional custom data to provide extra context for bug tracking that is unique to your application and business.
Find answers to the key questions: Which users are experiencing this bug? What was the value of their shopping cart?
The average cost of network downtime is around $5,600 per minute — or $300,000 per hour.
1 out of 5 online shoppers will abandon their cart because the transaction process was too slow.
On average, a two-second slowdown in page load decreases revenues by 4.3 percent.
Sentry supports every major language, framework, and library. You can browse each of them here.
You can get started for free. Pricing depends on the number of monthly events, transactions, and attachments that you send Sentry. For more details, visit our pricing page.
Sentry doesn’t impact a web site’s performance.
If you look at the configuration options for when you initialize Sentry in your code, you’ll see there’s nothing regarding minimizing its impact on your app’s performance. This is because our team of SDK engineers already developed Sentry with this in mind.
Sentry is a listener/handler for errors that asynchronously sends out the error/event to Sentry.io. This is non-blocking. The error/event only goes out if this is an error.
Global handlers have almost no impact as well, as they are native APIs provided by the browsers.
Here’s a quick look at how Sentry handles your personal information (PII).
×We collect PII about people browsing our website, users of the Sentry service, prospective customers, and people who otherwise interact with us.
What if my PII is included in data sent to Sentry by a Sentry customer (e.g., someone using Sentry to monitor their app)? In this case you have to contact the Sentry customer (e.g., the maker of the app). We do not control the data that is sent to us through the Sentry service for the purposes of application monitoring.
Am I included?We may disclose your PII to the following type of recipients:
You may have the following rights related to your PII:
If you have any questions or concerns about your privacy at Sentry, please email us at [email protected].
If you are a California resident, see our Supplemental notice.