C++ console application in Visual Studio 2005.
Debug build runs fine from inside the IDE. When debug build is run outside the IDE it returns error codes and terminates.
Same exe, right? Why would this be?
Printable View
C++ console application in Visual Studio 2005.
Debug build runs fine from inside the IDE. When debug build is run outside the IDE it returns error codes and terminates.
Same exe, right? Why would this be?
Perhaps, your exe needs something that not exists outside the IDE?
Is you PATH set correctly? IIRC, you can set/add to the PATH from within the IDE.
Viggy
Let me clarify a little:
This program exercises and tests database operations, checking return values for accuracy. It's not accessing a separate database file... the test program does everything in memory.
The debug version run from within the IDE successfully completes all tests and finishes without errors.
The debug version run stand-alone (outside the IDE) gets through about 2/3 of the database tests then fails and terminates.
I can understand differences between debug and release, but this is debug vs debug, again same exe, same binary, same instruction set.
Well, then where does the database exist? :confused:Quote:
Originally Posted by majoob
One difference between running the exe from within the IDE and without is, that IDE sets the current directory of the exe to the project folder (where you have all those cpp & h files) and running the exe normally (e.g. double-click) the current directory is the current directory :). This can have some unsuspected effects if you are using relative paths like
CString StrFilePath = _T(".\\my_file.xml");
Hope this helps,
Regards,
Usman.
I'd tend to suspect a memory allocation problem since memory allocation is probably subtlely different when running in the debugger. Can't be more specific though, I'm afraid.
Your application has a bug, plain and simple.Quote:
Originally Posted by majoob
"My app works on one machine, but not another"
"My app works when I uninstall <whatever>, but not otherwise"
"My app worked yesterday, but today it crashes".
etc...etc...
Your situation is just a variation on the same theme. You run it in one environment, works, another environment doesn't work.
This sounds like a memory overwrite in your application, or some other issue that isn't obvious (threading maybe?). But the bottom line is that your situation is not unique, as it happens to every programmer at some point.
Regards,
Paul McKenzie