Facilitating the analysis of software crashes is a costly and complex process. Building off of Backtrace’s recent launch of Breakpad / Crashpad / minidump support, I’m excited to discuss some of the new features that we have introduced over the last few weeks to help our users simplify this flow.
In this post, you’ll find out information about the following:
- Query Builder
- Scheduled E-mail Reports
- New Workflow Integrations
- Dynamic Symbol Downloads
This July, Backtrace was eager to head west to San Francisco as a first-time sponsor and exhibitor at NodeSummit. With somewhere between 800 and 1000 attendees, NodeSummit is the largest conference focused exclusively on Node.js, and is referred to as, “The Ecosystem of Node.” Knowing that in an ecosystem, each organism has its own niche or role to play, it was important that we knew what ours was. As Backtrace now offers turn-key crash management for the Electron App, we were specifically looking to engage and interact with the Electron developers at NodeSummit.
For our perceptive clients, you might have noticed that historically we’ve written robust release notes for our server components, but we haven’t included release notes for our web UI which we call Console. Now that more of our users are adopting Console as the primary means to manage, understand, and resolve crashes with Backtrace, we’ve decided to diligently update our community with Console release notes.
Check them out to find the latest updates to our web UI.
Backtrace now includes a completely new storage and indexing subsystem that enables engineers to slice and dice hundreds of attributes in real-time easily so they can better triage and investigate errors across their ecosystem, all from the comfort of their command-line environment. When an application crash occurs, there are hundreds of data points that may be relevant to the fault. This can range from application-specific attributes, such as version or request type to crucial fault data such as crashing address, fault type, garbage collector statistics to environment data such as system memory utilization.
Read on to learn more how you can interact with Backtrace from the command line for crash report and error investigation.
This is the first of a two-part series describing the implementation of a generic debugging tool. Part one covers the core internals of a debugger; part two focuses on extending a debugger to support a specific programming language — Go. Implementing a debugging tool may seem like a monumental task. gdb, one of the most… Read More