Visual Studio also contains a very powerful, and if not easier, debugger.
You can get it for free at http://www.microsoft.com/Express/.
But you should try out for yourself if it's to your liking. No sense in using something that you don't like.
do i have to install the compile the app from source code to use it?
compiling from source is not a viable option in the long term.
i don't know how windbg works either, as obviously i'm not familiar with it yet.
i expect it will not work 100% until i switch to MSVC++ since i use BCB, but it's better than nothing.
The debugger inside Visual Studio doesn't really require you to compile with the Visual C++ compiler per se... just as windbg, it works fine by attaching to executables.
However, I know the VS debugger requires program database files (aka debug files) for being able to properly debug (or you'll just get assembly output). Maybe this can be generated from other compilers too, but I don't know for sure.
Otherwise, VS is not a bad idea and VC++ is not a bad compiler, if you have the option to switch and try it out.
i would love to, but unfortunately i don't have that option as i don't have the available time to do the port
"Do the port"? I don't understand what you mean by that, but...
You do realize that standards compliant code will compile in any compliant compiler, yes?
Anyway, I'm going to trust you have your reasons. Unfortunately, the rest of how to make it work is beyond my knowledge.
i've made extensive use of features that i believe are specific to BCB, namely their GUI components.
Well isn't that just more or less their version of MFC? I am not qualified to answer that question on my own since I do not have a PhD in proprietary useless libraries. Which also means I am not welcome to work at Microsoft. Its listed as one of their basic requirements.
WinDbg has a very good help file.
Use it to run the program in it's current location, then just let it catch the exception when it crashes.
Then go looking to see where the problem is.
If you compile the project in visual studio, so that it also outputs a .pdb file, then you should have full source code as well.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
He says his code cannot be easily moved over to VC++. I bet it may be easier than he suggests.
i'm pretty sure it's this now:
nm false hope
Last edited by m37h0d; 09-19-2008 at 08:44 AM.
i omitted a critical detail
this only happens on a certain computer setup - they're a celeron Ms with XP embedded IIRC.
doesn't happen on my development PC.
Make sure that the account your application is running under can write to %ProgramFiles%, because normally, an application SHOULD NOT write to it's install directory. %ProgramFiles% could be write protected in your execution environment.
Use SHGetFolderPath to find a folder suitable for writing data. APPDATA or LOCAL_APPDATA comes to mind.