incubator-stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Lemings" <Eric.Lemi...@roguewave.com>
Subject _RWSTD_REQUIRES throwing uncaught exceptions in tests?
Date Wed, 19 Mar 2008 22:24:10 GMT
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.
 

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message