Produced by the unexpected circumstances for c00000fd in address c821aob 7 (kernel32! The GetTickCount)

Delphi5 development, only occasionally an error, do not know what to quote

CodePudding user response:

GetTickCount will not make a system call, directly from the process of a value is returned to the application of the memory of, therefore, the cause of the error, is likely to be Hook

CodePudding user response:

That excuse me upstairs, how to solve?

CodePudding user response:

Occasionally make a mistake, the vast majority of normal word, use the following this method emergency

 
For I:=1 to 10000 do begin 
Try 
Xx:=GetTickCount (); 
Break; 
Except, 
end; 
end; 

Actually should be restored GetTickCount function in the first five or six byte, and restore the jump table address, to make the hooks.

CodePudding user response:

But I didn't call GetTickCount function, it is communication, should be the system automatically calls the function, in the event viewer to see quote this error

Is the try
RecStream:=TWinSocketStream. Create (csSocket Socket, iWaitTime * 1000);
Try
FillChar (cRecBufs, iRecLen + 1, 0);
If RecStream. WaitForData (iWaitTime * 1000) then
The begin
Result:=BR_RECEIVE_FAILED;

.
This code may be calling the function, to article, that how to solve?

CodePudding user response:

This problem is a bit complicated,

Error while debugging? Error or client?

CodePudding user response:

No debugging, every day, but it was difficult in the test, only when the production, there will be 2-3 times, the application will die, and then under the event viewer will see this error, but not to be applied to capture the most depressing this wrong, in a machine, but to change the machine error is not the wrong again, at the wrong machine is a server, and is window2003 system,

CodePudding user response:

Should be wild pointer access issues,
Reweave a application with debug information, plus TJvDebugHandler or Eurekalog or other similar stack information output tools, record call stack information when something goes wrong, so easy to tracking error source,

refer to 6th floor u013031552 response:

no debugging, every day, but it was difficult in the test, only when the production, there will be 2-3 times, the application will die, and then under the event viewer will see this error, but not to be applied to capture the most depressing this wrong, in a machine, but to change the machine error is not the wrong again, at the wrong machine is a server, and is window2003 system,