LastSword
Prince
- Joined
- Feb 24, 2013
- Messages
- 1,119
Each time I encountered a repeatable crash I took a savefile and reloaded it on machine where I compile dll for a project.
There I could use a debugger (VS 2010) and it would show me an exact line in a code (even allowed to trace steps back in methods).
Now a debugger shows me some hex codes, dll files and a general issue (not allocated memory...).
I am forcing an error by adding religious pressure of non-existent religion to a city (therefore I know that error happens in gameplay dll).
The plausible big difference is that I have installed some VS 2019 stuff (Studio Tools for Applications). Maybe some directories were messed up?
@Edit
Well, a plausible fix:
-Include .pdb file in the same folder as .dll (Import into VFS).
-Use debugger to attach to process (civilization 5.exe) after game load. I have used Visual Studio 2022 (2008 do not seem to attach at all).
There I could use a debugger (VS 2010) and it would show me an exact line in a code (even allowed to trace steps back in methods).
Now a debugger shows me some hex codes, dll files and a general issue (not allocated memory...).
I am forcing an error by adding religious pressure of non-existent religion to a city (therefore I know that error happens in gameplay dll).
The plausible big difference is that I have installed some VS 2019 stuff (Studio Tools for Applications). Maybe some directories were messed up?
@Edit
Well, a plausible fix:
-Include .pdb file in the same folder as .dll (Import into VFS).
-Use debugger to attach to process (civilization 5.exe) after game load. I have used Visual Studio 2022 (2008 do not seem to attach at all).
Last edited:
