Hi Viktor, It is a summary of a long way hunting/debugging, so these short sentences/fragments are not adequate to describe the fix. But, as I see this is an usual way for fixing, without so much details.
Please test it in MinGW environment, should fix some errors mainly in object handlings regarding the Heap managements. Best regards, István -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Viktor Szakáts Sent: 2010. január 2. 22:58 To: Harbour Project Main Developer List. Subject: Re: [Harbour] SF.net SVN: harbour-project:[13444] trunk/harbour Hi Istvan, > Log Message: > ----------- > 2009-01-02 21:59 UTC+0100 Istvan Bisz (istvan.bisz/at/t-online.hu) > * /src/vm/fm.c > * Not adequate defitions of the subsequent CRT functions for the MinGW implemetations: > #ifndef USE_DL_PREFIX > #define dlcalloc calloc > #define dlfree free > #define dlmalloc malloc > ... > #endif /* USE_DL_PREFIX */ > The malloc/free CRT functions should'nt be redefined in this way. Just a general note: It would be nice to see in your change descriptions what is actually fixed. I mean what was the observed error before the fix. Now I can't even test it, as it always worked for me even so far, don't know how to verify the improvement. > * The mesage: "Warning, memory allocated but not released..." is sent on request (//INFO cmdarg). But this way the text of the message is misleading. IMO it should only be displayed if there _are_ unreleased blocks. Saying "Warning, memory allocated but not released: 0 blocks" looks like a display bug. IMO it was good as it was, or I'm missing something. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour _______________________________________________ Harbour mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
