My small white, maintain a Delphi project, encounter a problem a problem under caused the problem to stop working correctly , then applied directly out of the, the project triggered is calling a method

The begin
If sdFileName. Execute then
The begin
LsFilename:=sdFileName. FileName;
Dbg_inner_fk. ShowBands:=True;
Dbg_inner_fk. SaveToXLS (lsFilename, False);
Dbg_inner_fk. ShowBands:=False;
end;

UGlobalFunc. MsgDlg (' file successfully! ', mtInformation);
end;


Procedure TdxDBGrid. SaveToXLS (const AFileName: String; ASaveAll: Boolean);
The begin
DxGrExpt. SaveToXLS (Self, AFileName ASaveAll);
end;


Is a occasionally appear problem, ask god to help and give the younger brother some direction,

CodePudding user response:

Debugging errors stick call stack information, your problem is you posted above the two functions?

CodePudding user response:

Thread the Start: the Thread ID: 8360. The Process TopClientShell. Exe (8756)
The Module Load: MSFTEDIT. DLL. No Debug Info. The Base Address: $60 d40000. Process TopClientShell. Exe (8756)
The Module Load: WPDSHEXT. DLL. No Debug Info. The Base Address: $51 ca0000. Process TopClientShell. Exe (8756)
The Module Load: SHMEDIA. DLL. No Debug Info. The Base Address: $5 dd20000. Process TopClientShell. Exe (8756)
The Module Load: WMVCore. DLL. No Debug Info. The Base Address: $51 a30000. Process TopClientShell. Exe (8756)
The Module Load: WMASF. DLL. No Debug Info. The Base Address: $5 dce0000. Process TopClientShell. Exe (8756)
Thread the Start: the Thread ID: 9032. The Process TopClientShell. Exe (8756)
Thread Exit: the Thread ID: 9032. The Process TopClientShell. Exe (8756)
The Module to Unload: MSFTEDIT. DLL. Process TopClientShell. Exe (8756)
Thread the Start: the Thread ID: 5080. The Process TopClientShell. Exe (8756)
Thread Exit: the Thread ID: 8360. The Process TopClientShell. Exe (8756)
The Module to Unload: SHMEDIA. DLL. Process TopClientShell. Exe (8756)
The Module to Unload: WMVCore. DLL. Process TopClientShell. Exe (8756)
The Module to Unload: WMASF. DLL. Process TopClientShell. Exe (8756)
The Module to Unload: WPDSHEXT. DLL. Process TopClientShell. Exe (8756)



This is the trigger events [export] debugging information, and without an error, the project has been launched, and develop UAT is no problem, and only in the user operation occasionally appear problem,

CodePudding user response:

What's on??
Debugging errors stick call stack information,

CodePudding user response:

reference fang098 reply: 3/f

what's on it??
Debugging errors stick call stack information,

Ask, how the call stack information, and in addition, calls without error, your test is good, get the problems on the user's machine

CodePudding user response:

reference fang098 reply: 3/f

what's on it??
Debugging errors stick call stack information,

Die process, restart the application, one or more, can be successfully exported file, not failed every time

CodePudding user response:

Program and log output, to get the user's machine test, can according to the log screen what line of code is out of question,
The most bad checked the occasional problem, want to have patience, personally, I estimate is related to the environment,

CodePudding user response:

reference 4 floor gugll response:

Quote: reference fang098 reply: 3/f

What's on??
Debugging errors stick call stack information,

Ask, how the call stack information, and in addition, the call without error, the user test is good, oneself take problems in machine

Test is to simulate the user environment to test, of course, put your program in the machine is not installed the development environment,
To the next windbg to load your application will print out your application to use the library, and will wait for you at this time of debugging after running behind the wrong you can view the call stack information,
The information shown in the figure below