AmiBroker features a system of detecting and reporting bugs called "Crash recovery system". The name suggests that AmiBroker is now able to recover from such unexpected situations and indeed it can!.
How could this be done? Well... some tricks are needed to wrap the exception handling mechanism used by Windows :-)
Normally when Windows application performs some illegal memory access, illegal operation (for example division by zero) or illegal instruction the system pops the dead-end message box saying "This program has performed an illegal operation and will be shut down". Now you have got no choice - the application is terminated when you click on OK button.
AmiBroker's crash recovery system introduced in v3.47 beta intercepts the exception generated by Windows and instead of standard dead-end message box it displays the following dialog:
As you can see there is a window that displays important system information and there are five buttons Try to recover, Exit program, Copy to clip, Troubleshoot, Send report. Clicking on the Exit program button works exactly the same as clicking on "OK" button in the standard Windows dead-end message box. But the first two buttons give you brand new possibilities. If you click on Try to recover button AmiBroker will try to recover from the error and continue running. In most cases you will be able to save your work and modifications you have made so you will not lose anything. In fact you will be able to work normally. There are however some cases when recovery will not succeed and AmiBroker may be unstable, so it is advised just to save your data and exit. It may also happen that this window will pop up for a couple of times - then you should just click on Try to recover several times. Copy to clip - copies bug report details with system information to clipboard so you can paste this information in e-mail program and send it to us.
The recover function is quite nice but the main purpose of this system is to find and fix the problems in future version and this is why the most important function was provided - Send report. If you the crash recovery window popped up on your screen please click on Send report button before attempting to continue work. This will automatically send the details shown in the crash recovery window to us. Please do add your e-mail (in Your e-mail field), so we can respond to your report. If you do not provide e-mail, the report will be sent anonymously, but we won't be able to respond to it and provide you any guidance.
AmiBroker version 18.104.22.16899
( cooltool.dll 5.29.9, mfc42.dll 6.6.8063, msvcrt.dll 7.0.7600 )
Microsoft Windows 7 version 6.1 (Build 7600)
Service Pack 0.0
Common Controls: 6.16
Description: ACCESS VIOLATION
Exception occurred during AFL formula execution at address: 77E7317F, code: C0000005
Detailed exception information:
Broker.exe caused an EXCEPTION_ACCESS_VIOLATION in module ntdll.dll at 0023:77E7317F, RtlImageNtHeader()+0411 byte(s)
0023:77E7317F ntdll.dll, RtlImageNtHeader()+0411 byte(s)
0023:77E73407 ntdll.dll, RtlImageNtHeader()+1059 byte(s)
0023:77E732F2 ntdll.dll, RtlImageNtHeader()+0782 byte(s)
EAX=071BD978 EBX=071BCDA8 ECX=00000000 EDX=00000000 ESI=071BD970
EDI=071B0000 EBP=00000000 ESP=0018F490 EIP=76D18FBA FLG=00010246
CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B
AFL Parser status:
Processing stage: EXCEPTION
Formula ID: 1995 (Unnamed 190)
Action 1 (INDICATOR)
Number of stock loaded: 35
Currently selected stock: MCD
Number of quotes (current stock): 751
Data source = (default), Data local mode = 1, NumBars = 250
Data source = (local), Data local mode = 1, NumBars = 1000
2783 - Preferences settings--Preferences
2824 - Shows AFL formula editor--Formula Editor
Cache manager stats:
Number of list elements: 1
Number of map elements: 1
Hash table size: 5987
MemoryLoad: 25 %
TotalPhys: 4194303K AvailPhys: 4194303K
TotalPageFile: 4194303K AvailPageFile: 4194303K
TotalVirtual: 4194176K AvailVirtual: 4029976K
Last Windows message:
As you can see AmiBroker generates itself most important details for the bug report including even some history of menu selections (Command history) but the most essential thing at this point is to provide the description of steps needed to reproduce the bug. It would be nice if you could send us also the e-mail with the description of steps required to reproduce the problem (what you have done before the bug occurred, what special conditions must be met to reproduce it, maybe an AFL formula that you have tried and anything that you suppose might be important (even though AmiBroker includes a few lines of offending formula automatically)). This is critical since automatically generated information is very nice but can not cover all the details.
Clicking Troubleshoot brings up Troubleshooting page at http://www.amibroker.com/troubleshoot.html that contains descriptions of most common problems and how to solve them.
Some final notes: I have put significant amount of work in making this system reliable, however you should be aware that not all exception and/or system errors could be handled by this system and it may happen that AmiBroker will not be able to recover from some fatal error. It is also possible that this system would not be able to intercept all low level exceptions. In that case just prepare the report by yourself giving me as much details as possible.
Please remember that the final goal is making AmiBroker rock-solid and bug-free. This is what I am working on constantly.