We have a vc + + development program, starting with a certain probability will collapse, associated with running the host environment, it is easy to appear some computer, some never appeared, there was a bug, debugging stack is shown in the load dynamic library, which sentence couldn't locate the code problem, ask everybody to give some advice, thank you very much, the stack information is as follows:


Applications use Codejock Software loadskin module, see the DLL injection of loadskin source code contains a lot of by loading dynamic library operation, a little doubt is the problem here, but no specific reason,

CodePudding user response:

Don't try to load the DLL, probably this DLL has a problem

CodePudding user response:

This DLL is system load, could not load

CodePudding user response:

http://blog.csdn.net/zhao4zhong1/article/details/53078924 old drivers find bug decade journey

CodePudding user response:

Output information as shown above, it seems is the library that sogou and an cjstyles libraries have conflict, I don't know whether that is?

CodePudding user response:

VS debug menu under open the Win32 C0000005 anomaly, test and operation in Cxx5 collapse when it will clear up in the melt point, combining the call stack solution to modify code

CodePudding user response:

Reply to fifth floor, error is in the system of the DLL, there is no stack information can be analyzed

CodePudding user response:

In the stack screenshots NTDLL. DLL is down?

CodePudding user response:

refer to 6th floor hjirt528825 response:

reply 5 floor, error is the DLL in the system, there is no stack information can be analyzed

Tend to do bad things and bad luck is not a person
So the wrong place is not necessarily the fault point
Can consider through log or gradually commented code
To locate the problem

CodePudding user response:

refer to 7th floor zgl7903 response:

in the stack screenshots NTDLL. The DLL is down?

No down stack

CodePudding user response:

refer to the eighth floor xian_wwq response:

Quote: refer to the sixth floor hjirt528825 response:

Reply to fifth floor, is wrong in the system of the DLL, there is no stack information can be analyzed

Tend to do bad things and bad luck is not a person
So the wrong place is not necessarily the fault point
Can consider through log or gradually commented code
To locate the problem point

Bugs and not every time will now, sometimes don't appear a few days, so it is difficult to see through the commented code error

CodePudding user response:

Sogoupy this DLL may have a problem