Crash Issue

[lerxst2112]

You are doing it incorrectly.

Under C/C++ -> General you need Debug Information Format set to Program Database, and under Linker ->Debugging you need Generate Debug Info set to Yes, and a valid filename in Generate Program Database File if there isn't already one there.

[Randymarsh9]

Alright, it works now. Thank you very much.

[Randymarsh9]

Actually, I cannot get the debugger to attach to zone.exe. The only options for debugging are start new instance or step into new instance and both just tell me that zone.exe is not running even when it is.

[lerxst2112]

Debug -> Attach to process, pick the one with the process id you want. It's part of the name of the log file. If you go to that zone and use some # commands you can see which number command log is newest and pick that one.

[Randymarsh9]

Ok, I must be doing something wrong. I have zone set to build releasebots, I went into zone's properties and changed debug information format to program database (/Zi), set Debugging to yes in linker/debugging and made sure it is generating a file, built the solution, moved over all of my normal .exe files and the zone.pdb file into my build. When I right click on zone and go to debugging though, there is no option to attach to process. It just says start new instance which gives an error message. Do I have to load in the processes or change where it is looking or something like that?

[lerxst2112]

Have the zone running
In Visual Studio with the solution loaded, select Debug -> Attach to Process... from the menu. I don't know what you mean when you say you click on zone and go to debugging.
Select proper process in the list according to the instructions above.
Make it crash
Post the call stack from the call stack window which is generally on the lower right. You can also press Alt-7 to find it, or select Debug -> Windows -> Call Stack.

[Randymarsh9]

I was referring to right clicking zone in the solution explorer so display options like clean, build, and debug. The issue that I had was in the version of visual studio I am using, attach to process is not actually a command in debug when you select it on the task bar. I had to go to tools->Customize->Commands->Menubar:debug->Add Command->Debug->Attach to Process (This is just in case someone else ever has trouble finding attach to process as well). I got it working though and figured out what was causing the zones to crash. Thanks for the help.