Mailing-List: contact dev-help@stdcxx.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@stdcxx.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C88A0F.F45418D7"
Subject: _RWSTD_REQUIRES throwing uncaught exceptions in tests?
Date: Wed, 19 Mar 2008 16:24:10 -0600
Message-ID: 
 <CFFDD219128FD94FB4F92B99F52D0A49010A3675@exchmail01.Blue.Roguewave.Com>
Thread-Topic: _RWSTD_REQUIRES throwing uncaught exceptions in tests?
Thread-Index: AciKD/REJo8sn5sKQ7OA6F407YiG+Q==
From: "Eric Lemings" <Eric.Lemings@roguewave.com>
To: <dev@stdcxx.apache.org>

------_=_NextPart_001_01C88A0F.F45418D7
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Greetings,
=20
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 >=3D 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).
=20
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.
=20
Brad.
=20

------_=_NextPart_001_01C88A0F.F45418D7--