In stark contrast to a rather snowy March in NYC, we experienced beautiful weather during our visit to San Francisco for GDC 2017. We designed a booth stocked with old video game references, fun puzzle giveaways, chocolate gold coins to sustain visitors throughout the day, and a Nintendo Switch raffle. Most importantly, four of us from Backtrace attended and were eager to meet game developers to chat about debugging challenges.
A new integration wizard has just been released, allowing you to more easily integrate your applications into Backtrace. The wizard guides you through the steps of creating a new project, integrating an application and introduces you to other value-add features such as workflow integrations. Look below to see a live demo of how we process firefox crash dumps with symbolification in a matter of seconds.
Most users of Backtrace automatically submit error and crash reports, however some users just want to manually upload a few dumps from environments where automated submission is turned off. It is now possible to do this directly through our web console with just a few clicks. Simply select “Trace Upload” menu item to upload one or more minidumps or Backtrace snapshots for processing. It is also possible to do this from the command-line with the morgue tool. Read more to see a video of this functionality in action.
We’re thrilled to be attending GDC next week to meet with game developers and learn more about their debugging challenges. We’re exhibiting at booth 541. Come say “hi”, take home some free swag, and enter a raffle for an opportunity to win the grand prize: a Nintendo Switch! We’re also rolling out some new thematic booth content for… Read More
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.