RCov / RSpec segfaults on Ubuntu

Hi all,

I appreciate that this is not an RSpec question, but I wondered if
anyone out there can offer some pointers. We’re using the latest
versions of RSpec and RCov, and ruby --version says this (on the
Ubuntu build server):

ruby 1.8.6 (2008-07-17 patchlevel 279) [x86_64-linux]

We’re getting intermittent (yes, intermittent!) segfaults from the
build when running code coverage.

It works on my (OS X 10.4) machine :wink:

I can’t see how to report bugs with RCov - the FAQ ‘your question
here’[1] doesn’t offer my anywhere to type anything. It’s also
suggested elsewhere on the site that you can report issues on the
release notes page[2], and I can see plenty of other peoples’
feedback, but again I can’t see any way to offer any of my own.

I must be missing something really obvious here - can anyone help me
to get in touch with whatever RCov ‘community’ exists?

Failing that - any good resources / tips for working around these
segfault issues - any ‘no go areas’ we can just avoid in our specs? I
noticed, for example, that one of our projects consistently
segfaulted on this line:

/vendor/plugins/rspec/lib/spec/mocks/message_expectation.rb:41:
[BUG] Segmentation fault

Any pointers greatly appreciated.

cheers,
Matt

[1]eigenclass.org
[2]eigenclass.org


http://blog.mattwynne.net

In case you wondered: The opinions expressed in this email are my own
and do not necessarily reflect the views of any former, current or
future employers of mine.

I’ve got a version of rcov up at github (sudo gem install
spicycode-rcov --source=http://gems.github.com/) incorporating many of
the fixes for rcov segfaults. So far none of the old standard
crashes have crept back up. Give it a try and let me know how it
works for you.


Chad

Thankyou Chad and Aslak, those patches seem to have worked perfectly

  • time to apply the threshold crank! [rubs hands gleefully]

On 13 Sep 2008, at 16:50, Chad H. wrote:

wrote:

It works on my (OS X 10.4) machine :wink:
me to get
cheers,
of mine.
[email protected]
http://rubyforge.org/mailman/listinfo/rspec-users

cheers,
Matt

http://blog.mattwynne.net

In case you wondered: The opinions expressed in this email are my own
and do not necessarily reflect the views of any former, current or
future employers of mine.

On Sat, Sep 13, 2008 at 12:36 PM, Matt W. [email protected] wrote:

the site that you can report issues on the release notes page[2], and I can
see plenty of other peoples’ feedback, but again I can’t see any way to
offer any of my own.
I must be missing something really obvious here - can anyone help me to get
in touch with whatever RCov ‘community’ exists?
Failing that - any good resources / tips for working around these segfault
issues - any ‘no go areas’ we can just avoid in our specs? I noticed, for
example, that one of our projects consistently segfaulted on this line:
/vendor/plugins/rspec/lib/spec/mocks/message_expectation.rb:41: [BUG]
Segmentation fault
Any pointers greatly appreciated.

http://rspec.lighthouseapp.com/projects/5645-rspec/tickets?q=tagged%3Arcov
GitHub - spicycode/rcov: Home has moved to http://github.com/relevance/rcov (I believe this fixes
some of the problems)

Aslak