Farid Zaripov wrote:
-----Original Message-----
From: Martin Sebor [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 29, 2008 6:36 PM
To: [email protected]
Subject: Re: svn commit: r616003 -
/stdcxx/branches/4.2.x/tests/utilities/20.temp.buffer.cpp
[...]
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())?
Maybe it's reasonable for the _CRT_ASSERT reports, but, for example,
the _CRT_ERROR report is issued from abort() function. I'm not sure if
we
can invoke rw_fatal() from abort() :-)
Yeah, that might get us into an infinite loop. So it sounds like
on Windows we need to call whatever abort() calls after invoking
the hook. I.e., the observable behavior (from the POV of another
process) should be the same WRT exit status, etc.
Martin
Farid.
