Product Releases Update Our new Search tool allows you to quickly build detailed queries without having to leave the page. Our new search tool expands on our column filtering feature. You can now create even more detailed queries by filtering on 20 unique criteria. New for this release is the ability to search Call Stack Function Names, Call Stack File Names, and Call Stack Line Numbers.

Subkeying is a way to group a set of crashes at some level other than the top level of the call stack. Subkeying is a way to group a set of crashes at some level other than the top level of the call stack. At BugSplat, crashes are grouped by a stack key and groups of crashes can be found on the Summary page. By Default, BugSplat groups crashes using the topmost level of a call stack. A subkey is created when crashes are grouped at a level other than the top level of a call stack.

You’re in the process of creating and launching new softwareand you want it to be as stable as possible. Or, maybe your software has been running for a while, but you’re frustrated with the bug-reporting workflow in place. Either way it’s time to look for a crash reporting process that fits your application. This leads to a natural question: Should we build it? Or should we buy it? To expand on this question, which will be better for my business?

Most of us here at BugSplat spend the majority of our day at our computer. If you are reading this post, there's a good chance that you probably do too. And, like us, you probably expect that computers are just supposed to work for you. However, in my experience, this close relationship we share with our machines just expands the realm of possible annoyances we encounter day-in and day-out.