----- Original Message -----
From: "Steve Lee" <steve@...>
Sent: Wednesday, October 27, 2004 5:44 PM
Subject: Re: [Mingw-users] crtdbg.h and _ASSERT
> >I think that proving _ASSERT for MinGW is not simply a matter of
> writing the
>>header file (which you are free to contribute if you wish) because the
>>assertion failure handler _CrtDbgReport() is only present in msvcrtd.
>>not the msvcrt.dll that MinGW uses. Although MinGW already has an
>>library for msvcrtd.dll, AFAIK you can only use it if you modify
> the GCC
>>"specs" file because it currently always links with msvcrt.dll.
> Hi Luke,
> That sounds familiar though I don't have access to Microsoft tools
> or a debug DLL to check.
> As it stands then it is not so easy to port code that uses the features
> in msvcrtd. However there must a v. low demand so I don't think I
> will provide (yet). There is also a slight question over whether
> a user with msvcrt.dll will also have msvcrtd.dll but surely could
> assume that everyone will always have both?
No, I believe that msvcrtd.dll is only distributed with MSVC and other
Microsoft tools, and is not redistributable. If you are talking about
end-users of your application code though, you simply should not send them
executables that are linked to msvcrtd.dll. If you actually need
assert-style features in your release builds then you should write your own
error reporting functions.
> I don't really need to use the Microsoft C runtime debug facilities
> so I will recode to use something like the C standard assert behaviour.
> As long as assert has some UI in a debug build it will do :-)