GitHub Actions, SSH Debugging, and C Function Names in rbspy
Monday brought a long-desired feature to rbspy: identifying C functions in stack traces. Previously, when a C function appeared in the stack, rbspy labeled it simply as <c function> - unknown. The new pull request changes that by porting logic from Ruby's .gdbinit that can resolve actual C function names.
The PR's internals aren't fully understood yet, though a collaborative session with Tim and Mikkel helped make headway. A deeper write-up may follow once the implementation is better understood.
Debugging GitHub Actions Setup
While merging other rbspy pull requests, a cascade of issues surfaced. Travis builds had become noticeably slower at producing releases, prompting an attempt to migrate to GitHub Actions. The migration turned into an extended debugging session, a familiar frustration for anyone who has configured CI before.
The debugging process often felt opaque and time-consuming, matching past experiences with CI setup. However, a useful tip emerged from a Twitter thread: another developer shared their own GitHub Actions struggles, and a reply recommended the debugging with tmate action. This action enables SSH access directly into the CI environment, which could make troubleshooting significantly more straightforward.
