Crash running tests about cucumber-cpp HOT 2 CLOSED

Same problem running examples (BoostCalculatorSteps):
Program received signal SIGSEGV, Segmentation fault. 0x00000000005622e8 in cucumber::internal::CukeEngineImpl::stepMatches ( this=0x7fffffffe630, name=...) at (...)/cucumber-cpp/src/CukeEngineImpl.cpp:29 29 engineMatch.id = convertId(commandMatch.stepInfo->id);

Had to fix CukeEngineImpl.cpp:27 this time.
In fact, I returned a const ref in MatchResult and StepMatchesResponse classes, this avoids changing the code everywhere the accessor is called.

The good news is that tests and examples are running now.
Thank you for your work!

from cucumber-cpp.

I am not having those issues on Linux Mint 13 i386 (the old laptop I'm using now), but it would make sense even without the problems you are experiencing. I started using BOOST_FOREACH recently, so I was unaware of the nasty implications.

I like returning const refrences in getters as well. Since they are all internal interfaces (e.g. we are not breaking our code by doing const_casts!), I see no point in returning new objects there. Feel free to fork the project and submit a pull request to return const refrences for getters :-)

By the way, adding consts to methods was part of a general cleanup I was going to do for issue #31 on which I'm working.

from cucumber-cpp.