visual-studio-2003

How can I configure windows to generate a core dump from an application? I'm using Win xp, and the application is build with Visual Studio 2003. Microsoft has a free tool called Userdump.exe which will do this. It's pretty simple to use that tool to create a dump (.dmp) file for a process that shuts down with an exception or to create a dump file for a hanging process Just to throw in some other suggestions: ProcDump that is part of the MS SysInternals suite (it captures crashes but also does a load more, can take dumps if CPU usage spikes for an amount of time, etc) You can put code into your

Our previous development systems used Windows XP and Windows 7. Debugging C++ DLLs from Visual Studio worked great. A recent move to Windows 10 has resulted in an annoying problem. We can debug once (using F5 ), but the 2nd time results in a linker error: MyProg fatal error LNK1201: error writing to program database 'MyProg.pdb' Trying to delete the .pdb manually in Explorer while Visual Studio is still open results in the error: The action can't be completed because the file is open in devenv.exe It doesn't matter whether you hit a breakpoint or not. Just start debugging once results in the

When I build a Visual Studio project, the executable is written to the output directory specified in the projects Property Page. I have a project that has some extra files (e.g., .ini file) that are used by the program. How can I configure the project to copy the file to the output directory so that when the program runs, it has a copy of the other file in its CWD? I checked the Property Page of the file and there was nothing useful other than an option to exclude it from the build (which is disabled), and the custom-build-tool command is empty (plus it is a plain-text file that does not need