This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
libstdc++/9073: Can __STL_ASSERTIONS come back, but with more than rope?
- From: Matthias Klose <doko at net dot local>
- To: gcc-gnats at gcc dot gnu dot org, debian-gcc at lists dot debian dot org
- Date: Sat, 28 Dec 2002 00:34:00 +0100
- Subject: libstdc++/9073: Can __STL_ASSERTIONS come back, but with more than rope?
- Reply-to: 128993 at bugs dot debian dot org
>Number: 9073
>Category: libstdc++
>Synopsis: Can __STL_ASSERTIONS come back, but with more than rope?
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Fri Dec 27 15:36:02 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Anthony DeRobertis <asd@suespammers.org>
>Release: 3.0.4 (Debian) (Debian unstable)
>Organization:
The Debian Project
>Environment:
System: Debian GNU/Linux (unstable)
Architecture: i686
host: i386-linux
>Description:
[ 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.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: