A combine soldier entity shot the bullet (CNPC_CombineS).It crashed a jeep took damage (CPropJeep::OnTakeDamage).It crashed after a bullet was fired (CBaseEntity::FireBullets).If you don't see the callstack window, go to Debug menu > Windows > Callstack.
You can use the call stack window to find out what got you into this mess. If not, you'll see a load of assembly crap. Now, if the crash was in code you have power over, you'll see the code. Note: In Visual Studio 2010, press "Debug with Native Only" in the actions panel for this step. Press the start button (or F5) and it will recreate the crash, showing an error message, press Break. Now open the file, Visual Studio should start up. Grab the newest file and put it in the folder contaning your pdb files (If it crashed on your PC you can open it in place, moving it just fixes the paths so it can find the right files). It should contain at least one mdmp file. When you crash, look in your Half-Life 2 folder, the folder containing hl2.exe (This may be the HL2DM folder if you're using HL2DM as your mod's base). These are example files stored in every build:
For your mod, you can simply made a new folder for each release and put the files in there. You should keep the PDB files alongside every mod release. The PDB files change every time you compile. Having the file means you can see the code instead of trying to debug using assembly. pdb file contains pointers to all the source code from your project. pdb (Program Debug Database) files for server.dll and client.dll. If you want to find the dumps created when your mod crashes, those files are usually located in 'Steam\dumps\'. This file is like the black box recorder, it contains the last few moments before the program crashed. When a Source game crashes, it creates a mini du mp file. 2 What Do I Need to Open the MDMP File?.
0 kommentar(er)
