Quote Originally Posted by 2kaud View Post
in MainSequence (and SignalSequence), pVoid is NULL, so Main is NULL and de-referencing a NULL pointer will generate an error.
ok.

I have a doubt, today i received below errors from atlsimpstr.h,

1. nLength <=GetData() -> AllocLength

2. nrefs != 0

3. CStringData* pNewData = pOldData->Clone->Allocate(nLength, sizeof(XCHAR));
if(pNewData == NULL ) ThrowMemoryException


I refered https://social.msdn.microsoft.com/fo...dialog-pointer.
From this link, i have a doubt from string handling.
I'm guessing the assert has something to do with some CString manipulation you're doing probably in the destructor of the dialog class.
and confirmed using call stack.
To find out the variable that holds the culprit CStringData, you can click “Retry” when you see the assert dialog. This will start up your JIT debugger (e.g. Visual Studio or windbg) to attach to the process. After the debugger is attached, open the call-stack window. (In Visual Studio, the call-stack window can be opened in Debug menu ->
Windows -> Call Stack).
Is the problem is nonproper handling of String?