[ask for]The way for Solving "Microsoft Visual C++ Runtime Library" Error.
-
When I excute the developing program in VC6.0 debugging enviroment,the program run successfully.But when I excute the program of release version alone,appear the error infomation below: microsoft Visual C++Runtime Library Runtime Error! Program: C:\Progra.... This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. However,the program of previous release version excute successfully.why? I need your help and suggestion,thanks.
-
When I excute the developing program in VC6.0 debugging enviroment,the program run successfully.But when I excute the program of release version alone,appear the error infomation below: microsoft Visual C++Runtime Library Runtime Error! Program: C:\Progra.... This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. However,the program of previous release version excute successfully.why? I need your help and suggestion,thanks.
onlysaint wrote:
When I excute the developing program in VC6.0 debugging enviroment,the program run successfully. But when I excute the program of release version ... microsoft Visual C++Runtime Library
Hi, Please take a look at this article: www.flounder.com/debug_release.htm[^]
“Follow your bliss.” – Joseph Campbell
-
onlysaint wrote:
When I excute the developing program in VC6.0 debugging enviroment,the program run successfully. But when I excute the program of release version ... microsoft Visual C++Runtime Library
Hi, Please take a look at this article: www.flounder.com/debug_release.htm[^]
“Follow your bliss.” – Joseph Campbell
-
When I excute the developing program in VC6.0 debugging enviroment,the program run successfully.But when I excute the program of release version alone,appear the error infomation below: microsoft Visual C++Runtime Library Runtime Error! Program: C:\Progra.... This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. However,the program of previous release version excute successfully.why? I need your help and suggestion,thanks.
Firstly, both the debug builds and the release builds should be built with debug information. Some people erroneously believe that only release debug builds can be built with debugging information, but this simply isn't the case. Assuming you've got a release build with symbol files then proceed as you always would; break into the application with a debugger when the fault occurs and get a stack trace.
Steve
modified on Tuesday, March 2, 2010 8:30 PM
-
Firstly, both the debug builds and the release builds should be built with debug information. Some people erroneously believe that only release debug builds can be built with debugging information, but this simply isn't the case. Assuming you've got a release build with symbol files then proceed as you always would; break into the application with a debugger when the fault occurs and get a stack trace.
Steve
modified on Tuesday, March 2, 2010 8:30 PM
Stephen Hewitt wrote:
Some people erroneously believe that only release builds can be built with debugging information, but this simply isn't the case.
Umm... Surely, you wanted to say 'debug builds' instead?
“Follow your bliss.” – Joseph Campbell
-
Firstly, both the debug builds and the release builds should be built with debug information. Some people erroneously believe that only release debug builds can be built with debugging information, but this simply isn't the case. Assuming you've got a release build with symbol files then proceed as you always would; break into the application with a debugger when the fault occurs and get a stack trace.
Steve
modified on Tuesday, March 2, 2010 8:30 PM
-
Stephen Hewitt wrote:
Some people erroneously believe that only release builds can be built with debugging information, but this simply isn't the case.
Umm... Surely, you wanted to say 'debug builds' instead?
“Follow your bliss.” – Joseph Campbell
Yeah, that's what I meant.
Steve
-
I thought I did. I'll reiterate: Firstly ensure that the release build is built with debugging information. Then run the program under a debugger, break execution when the problem occurs and get a stack trace. Pick the thread that's displaying the runtime error message. Which part of this are you having problems with?
Steve