I learned that ruby ships with a .gdbinit file in the source repo, that permits inspecting the class/objects in the internals, basically handling the unpacking of the tagged ids for you, and saving the results as history items.
Of course I learned that after searching a few locations for "how to debug ruby" and finding a mix of snippets, most attributing a blog that's been offline for a year or two as the source, and a lot of two paragraph "here's how to start gdb" tutorials.
Kind of handy to have the tooling to debug the vm ship with the language sources!
I'm a fan of Open Source and have a growing interest in serverless and edge computing. I'm not a big fan of spiders, but they're doing good work eating bugs. I also stream on Twitch.
I learned that ruby ships with a .gdbinit file in the source repo, that permits inspecting the class/objects in the internals, basically handling the unpacking of the tagged ids for you, and saving the results as history items.
Of course I learned that after searching a few locations for "how to debug ruby" and finding a mix of snippets, most attributing a blog that's been offline for a year or two as the source, and a lot of two paragraph "here's how to start gdb" tutorials.
Kind of handy to have the tooling to debug the vm ship with the language sources!