On Thu, May 5, 2011 at 9:37 AM, Mark Rechler email@example.com wrote:
I’m wondering if it’s an issue with this particular patchset of ruby 1.8.7.
I bet so. Ruby development is kind of hot and heavy. We had a lot of
problems with p174 and I put a fair amount of work into tracking down
segfaults and backporting fixes. (see 188.8.131.52-1ubuntu1) It isn’t
easy, but saves the community a lot of work when they just get a
patched version through upstream through normal channels.
On Thu, May 5, 2011 at 9:18 AM, James firstname.lastname@example.org wrote:
Did you test the 1.8.7 package in frameos or rpm.aegisco.com against the
segfaulting mount provider?
Let’s be clear that the mount provider isn’t segfaulting, but ruby is.
If we could narrow down exactly when it happened to a particular line
of code, that would be awesome as it makes searching the upstream bug
tracker a lot easier. In some cases it is something more meta though,
like the garbage collector.