You most likely want to add debugging information to the release version if that is what is crashing. If zone.exe is all that's crashing then that's what you should focus on.
- Open the solution in Visual Studio.
- Select Release or ReleaseBots in the dropdown at the top.
- Right-click zone in the solution window and select properties.
- In the property pages, find C/C++ and change Debug Information Format to Program Database (/Zi)
- Under Linker/Debugging change Generate Debug Info to Yes (/DEBUG)
- Compile
- Copy all of the normal executables to your server directory along with zone.pdb
From here it depends on how you can duplicate the problem.
If it is easy to reproduce then start the server and get your toon that can cause the crash to the zone. Look in the logs folder to find what the process ID is for the zone you are in. It's the number in the log file name. In Visual Studio select Debug->Attach to Process and find the zone.exe that has the same number as the log file. Make it crash, copy the call stack from Visual Studio and post it if you can't figure it out yourself.
If it is not easy to reproduce then you will probably have better results with a minidump. Secrets posted information on how to force those to be generated by crashes. You open them in Visual Studio, click the green arrow, and it will show you where the crash occured.
Threaded Mode
