Debugging scary crashes of

@mperham and finally,

Debugging scary crashes of Rubinius Dirkjan Bussink 04 January 2012 Bugs, we all are in the infinite fight of getting rid of them. Sometimes they are trivial, other times a bit harder. In this video I’m going to show how I have been debugging an issue that caused memory corruption of your dear Ruby objects in Rubinius. Background It’s a pretty long video clocking at 55 minutes but I’m trying to be detailed in the discovery process. I’m explaining the steps I’m taking along the way and explaining why I’m taking those. The real debugging process if of course littered with taking wrong turns so please don’t think I’m brilliant and able to zoom into the issue immediately all the time. The video is not recorded as I was going through it the first time, so I exactly knew where I was going and which steps to take. If you want to look up some more information on GDB that I’m using...

Full article: http://rubini.us/2012/01/04/debugging-rubinius/