I say kind-of because there’s still a lot of Breakpad in there, but they’re more interested in building out tooling on top of it than improving Breakpad itself. Meanwhile, Google has kind-of moved on to Crashpad. Needless to say, we’re pretty invested in breakpad’s minidumps at this point.įast forward to the present day and in a hilarious twist of fate, products like VSCode mean that Microsoft now supports applications that run on Linux and MacOS so it runs breakpad in production and has to handle non-Microsoft minidumps somewhere in its crash reporting infra, so someone else’s extension of their own format is somehow their problem now! Mozilla helped out with this a lot because apparently, our crash reporting infrastructure (“Talkback”) was miserable circa 2007, and this seemed like a nice improvement. Those extensions became google-breakpad (or just Breakpad) which included a ton of different tools for generating, parsing, and analyzing their extended minidump format (and native Microsoft ones). Then Google came along (circa 2006-2007) and said “wouldn’t it be nice if we could make minidumps on any platform”? Thankfully Microsoft had actually built the format pretty extensibly, so it wasn’t too bad to extend the format for Linux, MacOS, BSD, Solaris, and so on. Microsoft Research has presumably developed a time machine to guarantee this. MiniDumpWriteDump’s supported versions are simply “Windows”. So long ago that their docs don’t even discuss platform support. Now you can turn a 100-thread coredump that would otherwise be 4GB into a nice little 2MB file that you can send over the internet and do postmortem analysis on. Oh and I guess if we’re taking the time, let’s stuff some metadata about the system and process in there too.Ĭongratulations you have invented Minidumps.
#Rewind symbol full#
A full coredump (all memory allocated by the program) is enormous - we can’t have users sending us 4GB files! Ok let’s just collect up the most important regions of memory like the stacks and where the program crashed. You want to know why your program crashed, but it happened on a user’s machine on the other side of the world. Background: What’s A Minidump, and Why Write rust-minidump? You are reading part 1, wherein we build up our hubris. how we got absolutely owned by simple fuzzing.what minidumps are, and how we made rust-minidump.
Which is why this is the story of how we did our best to make this nightmare as robust as we could and still got 360 dunked on from space by the sudden and incredible fuzzing efforts of article is broken into two parts: Unfortunately! Confidence! Is! Worth! Nothing! We’ve put a lot of effort into documenting and testing this thing, so I’m pretty confident in it! But if you want to read minidumps generated on a PlayStation 3 or process a Full Memory dump, you won’t be served quite as well. What I can say is that we have a very solid implementation of the core functionality of minidump parsing+analysis for the biggest platforms (x86, 圆4, ARM, ARM64 Windows, MacOS, Linux, Android).
This is a pretty fantastic result, but there’s always more work to do because Minidumps are an inky abyss that grows deeper the further you delve… wait no I’m getting ahead of myself. We did our best to isolate Breakpad, but still… yikes.) (And you know, isn’t a terrifying ball of C++ that parses and evaluates arbitrary input from the internet. Well actually in some sense I finished that work, because Mozilla already deployed it as the crash processing backend for Firefox 6 months ago, it runs in half the time, and seems to be more reliable.
Everything Is Broken: Shipping rust-minidump at Mozillaįor the last year I’ve been leading the development of rust-minidump, a pure-Rust replacement for the minidump-processing half of google-breakpad.
0 kommentar(er)
