CodePudding user response:

The DLL project?
//-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
//Important note about DLL memory management the when your DLL USES the
//the static version of the RunTime Library:
//
//If your DLL exports any functions provides that pass the String objects (or user-defined structs/
//classes containing nested Strings) as the parameter or the function results,
//you will need to add the library MEMMGR. LIB to both the DLL project and
//any other projects that use the DLL, You will also need to use MEMMGR. LIB
//if any other projects which use the DLL will be performing new or delete
//operations on any non - TObject - derived classes which are exported from the
//DLL. Adding MEMMGR. LIB to your project will change the DLL and its calling
//EXE 's to use the BORLNDMM. DLL as their memory manager. In these cases,
//the file BORLNDMM. DLL should be deployed along with your DLL.
//
//To get the using BORLNDMM. DLL, pass the string information using "char *" or
//ShortString parameters.
//
//If your DLL USES the dynamic version of the RTL, do not need to
//explicitly add MEMMGR. LIB as this will be done implicitly for you
//-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

CodePudding user response:

Is not a DLL project, it is an image processing program, and the error of time is uncertain, error may run for ten images, is also likely to run five is wrong

CodePudding user response:

Problem seems to be a pointer

CodePudding user response:

Seems to be visited an uninitialized object,