Comments on: GDC 2011: Crash Analysis and Forensic Debugging

By: Robert

Robert — Mon, 07 Mar 2011 22:29:09 +0000

Awesome presentation. We run into the exact same problems at my workplace, and while I didn’t actually glean too much new info, this was just about the best presentation I’ve ever seen on the topic. Mandatory viewing for our new hires

By: Chad Austin

Chad Austin — Sun, 06 Mar 2011 10:18:32 +0000

Great presentation! We solve a lot of the same problems at IMVU. I’ve written a series of blog posts on our techniques, including stitching stack traces out of C++ exceptions: http://chadaustin.me/tag/crashes/

I wanted to make it to your presentation but had a conflict… thanks for spreading the word! There’s definitely an attitude in some studios that “if we code it right, it won’t crash in the field”, but you have no control over what else is on the system…

By: Daniel

Daniel — Sun, 06 Mar 2011 04:29:41 +0000

Excellent talk. I spent a good chunk of last summer working with the breakpad library, and I ended up coding a 360 dump processor/stack walker and using XBWatson to watch for crashes, grab the minidump, and pop up a crash dialog on the user’s PC. It was really great having the same interface for handling crashes on PC and 360.

I would have liked to do the same thing with PS3, but it was a summer internship and I had to get back to finishing my undergrad.

By: GDC 2011 | .mischief.mayhem.soap.

GDC 2011 | .mischief.mayhem.soap. — Thu, 03 Mar 2011 03:06:32 +0000

[...] Crash Analysis and Forensic Debugging, Ellan Ruskin (Valve). Well, OK, more like a teaser, nothing there yet, but observe this space, Bookmark It [...]

By: Dustin Russell

Dustin Russell — Wed, 02 Mar 2011 22:52:59 +0000

Awesome talk!