Unhandled exception in ntdll.dll access violation reading location 0xFFFFFFFFFFFFFFFF
-
I get this message all of the sudden while I have a modless Cdialog and Richedit displayed When I switch the debugger to threads I see a number of ntdll.dll worker threads Can somebody point me in the right path Thanks
Just look at the Call Stack and find in this list your own (last called) module. Click on it to see what was your command/operation that caused the exception
-
Just look at the Call Stack and find in this list your own (last called) module. Click on it to see what was your command/operation that caused the exception
I did that went to the main thread (and looked at the stack) it pointed to thrdcore.cpp !::GetMessage(&(pState->m_msgcur line 155 Please note I have created 5 other Threads 4 UI threads which act as a wrappers for my Derived CAsynSocket Class and a regular worker thread Thanks
-
I did that went to the main thread (and looked at the stack) it pointed to thrdcore.cpp !::GetMessage(&(pState->m_msgcur line 155 Please note I have created 5 other Threads 4 UI threads which act as a wrappers for my Derived CAsynSocket Class and a regular worker thread Thanks
Access violation means that you're accessing memory that hasn't been allocated to your application ... so do the obvious. Go back a few steps on the stack and look at the sequence and look at all the pointer use and check 1.) The pointer is valid 2.) Is what it pointing at allocated 3.) If it is required that the structure it points to #0 terminated ... is it. Something in the last calls is failing one of those criteria, if need separate every pointer to a temp line of code in those sections and run a debug test on it.
In vino veritas
-
I get this message all of the sudden while I have a modless Cdialog and Richedit displayed When I switch the debugger to threads I see a number of ntdll.dll worker threads Can somebody point me in the right path Thanks
Without some more information about where this happened, the code that caused it, and the values of the variables involved, it is impossible even to make any suggestions. The only thing one can say is that you are using either an uninitialised variable, or one that has received an invalid value.
-
Without some more information about where this happened, the code that caused it, and the values of the variables involved, it is impossible even to make any suggestions. The only thing one can say is that you are using either an uninitialised variable, or one that has received an invalid value.
-
The strange thing Is there all these worker threads (ntdll.dll) that seem to have come up okay Thanks
ForNow wrote:
all these worker threads (ntdll.dll) that seem to have come up okay
But that does not mean anything. The only way to solve this sort of problem is by tracking back to the point where the fault is created. This may be a simple bug in your code, cross-thread corruption, or any one of a million other things happening.