Farid Zaripov wrote:
-----Original Message-----
From: Martin Sebor [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 29, 2008 6:27 PM
To: [email protected]
Subject: Re: svn commit: r616003 -
/stdcxx/branches/4.2.x/tests/utilities/20.temp.buffer.cpp
Farid Zaripov wrote:
-----Original Message-----
From: Martin Sebor [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 29, 2008 5:56 PM
To: [email protected]
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/[EMAIL PROTECTED]/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 :(
Wouldn't the _CrtSetReportHook() function work?
http://msdn2.microsoft.com/en-us/library/0yysf5e6(VS.80).aspx
I meant that it's not possible to know when we should abort and when
only print the message.
How about aborting on errors and assertions (e.g., by calling
rw_fatal()) and continuing on warnings (and calling rw_warn())?
Martin
Farid.
