I don't think this is a problem anywhere else, but check the nightly
builds: http://people.apache.org/~sebor/stdcxx/results/builds. Sounds
like a platform-specific problem.
That said, I do see a number failures in our regression tests, for
instance with Sun C++ 5.9 on Solaris 10/amd64:
21.string.assign.stdcxx-629
21.string.insert.stdcxx-630
21.string.insert.stdcxx-632
21.string.replace.stdcxx-170
21.string.stdcxx-162
Martin
Eric Lemings wrote:
Greetings,
I've been stepping through one of the string tests. The
std::string::at() member function is being called with a __pos value
that is >= size() causing the _RWSTD_REQUIRES assertion to fail. It
seems to be throwing an exception, which is not being caught, as a
result. Consequently, the whole test program raises an ABRT signal.
There are several such programs raising ABRT signals (on the Mac
platform at least).
Now there's certainly nothing wrong with the test case testing
out-of-bounds behavior but it should be catching any possible
exceptions, shouldn't it? Assuming the std::string::at() function does
not have a no-throw guarantee.
Brad.
