This is GCC Bugzilla
This is GCC Bugzilla Version 2.20+
View Bug Activity | Format For Printing | Clone This Bug
[ Reported to the Debian BTS as report #128993. Please CC 128993@bugs.debian.org on replies. Log of report can be found at http://bugs.debian.org/128993 ] It'd be nice to have __STL_ASSERTIONS or equivelant come back to do things like bounds-check vector accesses (yes, I know about at()) for debugging purposes. Release: 3.0.4 (Debian) (Debian unstable) Environment: System: Debian GNU/Linux (unstable) Architecture: i686 host: i386-linux
Responsible-Changed-From-To: unassigned->bkoz Responsible-Changed-Why: Mine.
State-Changed-From-To: open->feedback State-Changed-Why: __STL_ASSERTIONS making a comeback is extremely unlikely. A better way to do this would be to just encapsulate std::vector and add your own runtime checks. I believe that Cay Horstman has done this with older versions of std::vector: you might check google. -benjamin
State-Changed-From-To: feedback->suspended State-Changed-Why: Unlikely to be implemented any time soon.
This is fixed by the debug mode for libstdc++v3.