New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unreproducable crash of Fbserver.exe [CORE3673] #4023
Comments
Commented by: @hvlad 1. Could you produce full memory dump ? |
Commented by: Helmut Steinberger (helste) Hello Vlad, the error did occur today several times at the customers server. This is really a big problem. Please help me as soon as possible with a hint, what I can ckeck or what I cann do to mallow you check what this error comes from. Pleas give me a short answer, if you have red this and you are checking it. Kind regards Helmut Steinberger Here is a full logfile of drwtsn with hopefully enough information to track the error. |
Commented by: @dyemanov Moved the logs to attachments. |
Modified by: @dyemanovdescription: Hello, I have ocassionaly occuring fbserver crashes at our customers firebird server. I do not have any clue what could be the reason for this. Could you please help me identify the reason for this crashes? Kind regards Helmut Steinberger Here is the log: Microsoft (R) DrWtsn32 Anwendungsausnahme aufgetreten: *----> Systeminformationen <----* *----> Taskliste <----* *----> Modulliste <----* *----> Statusabbild für Threadkennung 0x420 <----* eax=0025ade8 ebx=00000000 ecx=0000006d edx=00000000 esi=00000000 edi=00000130 *** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\ntdll.dll - *----> Stack Back Trace <----* *----> Raw Stack Dump <----* *----> Statusabbild für Threadkennung 0x650 <----* eax=0000000f ebx=00000000 ecx=7c8250e2 edx=7c94847c esi=00000144 edi=00000000 Funktion: ntdll!KiFastSystemCallRet *----> Stack Back Trace <----* *----> Raw Stack Dump <----* *----> Statusabbild für Threadkennung 0xfcc <----* eax=00000000 ebx=00000000 ecx=0121fed8 edx=7c94847c esi=00000000 edi=0121ff18 Funktion: ntdll!KiFastSystemCallRet *----> Stack Back Trace <----* *----> Raw Stack Dump <----* *----> Statusabbild für Threadkennung 0x444 <----* eax=016fe860 ebx=7c947b8d ecx=00000005 edx=00000008 esi=00000000 edi=00000001 Funktion: ntdll!KiFastSystemCallRet *----> Stack Back Trace <----* *----> Raw Stack Dump <----* *----> Statusabbild für Threadkennung 0x628 <----* eax=00000001 ebx=7c949c98 ecx=7c949de9 edx=004c0000 esi=00000188 edi=00000000 Funktion: ntdll!KiFastSystemCallRet *----> Stack Back Trace <----* *----> Raw Stack Dump <----* *----> Statusabbild für Threadkennung 0x10c <----* eax=00696c4c ebx=0000003a ecx=aa5c87f5 edx=00000000 esi=0000019c edi=00000000 Funktion: ntdll!KiFastSystemCallRet *----> Stack Back Trace <----* *----> Raw Stack Dump <----* *----> Statusabbild für Threadkennung 0xfb4 <----* eax=00000102 ebx=00804210 ecx=7c821d43 edx=7c94847c esi=000001ec edi=00000000 Funktion: ntdll!KiFastSystemCallRet *----> Stack Back Trace <----* *----> Raw Stack Dump <----* *----> Statusabbild für Threadkennung 0x8a4 <----* eax=00000102 ebx=00d30bc4 ecx=0203fd68 edx=7c94847c esi=0000045c edi=00000000 Funktion: ntdll!KiFastSystemCallRet *----> Stack Back Trace <----* *----> Raw Stack Dump <----* *----> Statusabbild für Threadkennung 0x68c <----* eax=0bab0030 ebx=0264e0e8 ecx=00000025 edx=00000058 esi=00000310 edi=00000000 Funktion: ntdll!KiFastSystemCallRet *----> Stack Back Trace <----* *----> Raw Stack Dump <----* *----> Statusabbild für Threadkennung 0xf54 <----* eax=00000002 ebx=00000000 ecx=00e01610 edx=00e015f8 esi=00e015f8 edi=00000000 Funktion: ntdll!KiFastSystemCallRet *----> Stack Back Trace <----* *----> Raw Stack Dump <----* *----> Statusabbild für Threadkennung 0xbc4 <----* eax=0b2de0e8 ebx=00000000 ecx=0494dac8 edx=0421ffc8 esi=00e015f8 edi=00000000 Funktion: ntdll!KiFastSystemCallRet *----> Stack Back Trace <----* *----> Raw Stack Dump <----* *----> Statusabbild für Threadkennung 0x6cc <----* eax=0658f9f0 ebx=7c821c7b ecx=00000005 edx=0000000c esi=00000284 edi=00000000 Funktion: ntdll!KiFastSystemCallRet *----> Stack Back Trace <----* *----> Raw Stack Dump <----* *----> Statusabbild für Threadkennung 0x120 <----* eax=0a7af9c0 ebx=091c1484 ecx=00000000 edx=0a7afbe8 esi=0a7afbe8 edi=00000000 Funktion: fbserver!EXE_unwind *----> Stack Back Trace <----* *----> Raw Stack Dump <----* *----> Statusabbild für Threadkennung 0x144 <----* eax=0a48fcd0 ebx=00000000 ecx=0a48fd4c edx=0a48fcf8 esi=00e015f8 edi=00000000 Funktion: ntdll!KiFastSystemCallRet *----> Stack Back Trace <----* *----> Raw Stack Dump <----* => Hello, I have ocassionaly occuring fbserver crashes at our customers firebird server. I do not have any clue what could be the reason for this. Could you please help me identify the reason for this crashes? Kind regards Helmut Steinberger The log is attached. |
Commented by: @dyemanov You were asked about the memory dumps created by DrWatson, not only its log. Also, you haven't answered the second Vlad's question. |
Commented by: Helmut Steinberger (helste) Sorry for that. How can I produce a full memory dump? As for the 2nd question: The problem occures when printing and It could be that reportbuilder (reporting tool I use in my Delphi Application) does some multithreading. |
Commented by: @dyemanov The memory dump should have been created by DrWatson (if it was set up properly) and it should reside in the same directory as the log file. |
Commented by: Helmut Steinberger (helste) Memorydump was disabled. Now it is enabled but I have to wait for the error because it is not reproducable. |
Commented by: Helmut Steinberger (helste) This is the memorydump file. Had to splitt to 3 ZIP files. |
Modified by: Helmut Steinberger (helste)Attachment: memorydump.zip.001 [ 12073 ] |
Modified by: Helmut Steinberger (helste)Attachment: memorydump.zip.002 [ 12074 ] |
Modified by: Helmut Steinberger (helste)Attachment: memorydump.zip.003 [ 12075 ] |
Submitted by: Helmut Steinberger (helste)
Attachments:
WatsonLog1.txt
WatsonLog2.txt
memorydump.zip.001
memorydump.zip.002
memorydump.zip.003
Hello,
I have ocassionaly occuring fbserver crashes at our customers firebird server. I do not have any clue what could be the reason for this.
After inspecting the firebird.log of other customers, I discovered, that also other customers with different environment have the same crashes, but that crashes are very rarely. Sometimes there are months without crash, and then there are 4 or 5 crashes on 1 single day.
So I installed the debug build of firebird and now I have a log of the last crash (today).
Could you please help me identify the reason for this crashes?
Kind regards
Helmut Steinberger
The log is attached.
The text was updated successfully, but these errors were encountered: