ruby uses broken internal get/setcontext routines on precise/ARM
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ruby1.9.1 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Adam Conrad |
Bug Description
[Impact]
On precise/arm*, we had to disable ruby's testsuite so that it would build. The reason for this was that, at the time, precise's eglibc didn't have get/setcontext routines for ARM, and ruby was forced to select its own (broken) implementation instead.
Later in the precise development, eglibc grew support for get/setcontext on ARM, but we never rebuilt ruby to pick this up and fix itself. The obvious solution to this is to turn on the testsuite again and SRU so a rebuilt ruby fixes itself on ARM.
[Testcase]
If ruby passes its testsuite on both ARM builds, it's clearly ahead of where it was before, and that's pretty much all the test needed to prove the above is fixed.
[Regression Potential]
For all arches other than ARM, this is just a rebuild with precise's current toolchain. For ARM, this is a rebuild that will flip ruby from using a broken internal implementation to using a much saner glibc implementation of the same thing, so any potential for regression here is between nonexistant and tiny.
This is already fixed in Quantal, as newer versions of ruby have been synced from Debian since our eglibc was fixed.