stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Farid Zaripov" <Farid_Zari...@epam.com>
Subject RE: svn commit: r616003 - /stdcxx/branches/4.2.x/tests/utilities/20.temp.buffer.cpp
Date Tue, 29 Jan 2008 16:14:42 GMT
> -----Original Message-----
> From: Martin Sebor [mailto:sebor@roguewave.com] 
> Sent: Tuesday, January 29, 2008 5:56 PM
> To: dev@stdcxx.apache.org
> Subject: Re: svn commit: r616003 - 
> /stdcxx/branches/4.2.x/tests/utilities/20.temp.buffer.cpp
> 
> Farid Zaripov wrote:
> >   Earlier
> > 
> (http://www.mail-archive.com/stdcxx-dev@incubator.apache.org/msg03761.
> > ht
> > ml)
> > I proposed to convert MSVC CRT debug reports along with invalid 
> > parameter checking reports to the rw_xxx() reports.
> 
> I (vaguely) remember discussing this. For the memory errors, 
> I thing rw_error() or even rw_fatal() makes sense.

  The problem is that these reports may come from different places of
MSVC CRT
and we couldn't to know what the real reason of concrete report. We get
the only
the report severity (error, assertion, warning) and the report text.

> >   Or we can just print the report message into stderr, to not count 
> > these reports as other usual rw_errors and rw_asserts.
> 
> That would be another option. Although we should probably 
> abort on memory corruption errors.

  Unfortunately, it's not possible :(

Farid.

Mime
View raw message