New news:
The Windows build was compiled with embedded debugging info, which should help us find the lingering crashes.
Here is how this works:
We use the MS application DrWatson to capture and format a "Crash Dump". This dump is a small file which contains the state of the system at crash time. The dump file may be sent to me (NOT Microsoft and I can dissect it with the source code and maybe find the problem quickly.
Linux users are familiar with the same
concept of using gdb on a
core dump.
For those Windows users who want to give this a whirl, here goes.
1. First, configure DrWatson....
From Windows, Start->Run->drwtsn32
Set the following options:
Crash Dump Type: Mini
Dump Symbol Table
Dump Thread Contexts
Create Crash Dump File
Note the location of the Crash Dump Files for later. It is something like:
C:\Documents and Settings\All Users.WINDOWS\Application Data\Microsoft\Dr Watson
Click "OK"
2. The configuration need only be done once. Subsequently, you may start DrWatson with
Start->Run->drwtsn32 -i
DrWatson needs to be started only once per login session, and stays quietly in the background waiting for a crash.
3. Run
opencpn as usual. Try to create a crash. If you succeed, you will get the normal MS "
Opencpn Blah Blah needs to close...blah blah Send/Don't Send"
Click "Don't Send".
DrWatson wil capture a dump file.
In the folder location recorded in Step 1, you will find a file called "user". This is the dump file.
This is the file I need for diagnosis with source tools. Please
email attach this file to me directly.
I hope this effort will pay off in finding those pesky crashes, and we can move to Release of 1.3.4
Thanks all for your diligent testing and useful reports.
Especially I thank manimaul for the Bishop's hat and all the other cool art.
Better and better....
Enjoy....
Dave