General troubleshooting steps encountered with program crashes
1, debug the program, locate the crash to the code place. If it is a problem in the system code, you can copy the line code on Baidu Search, if you write your own code, then I think it is easier to change.
2, general we have encountered the program crashes online must be found, try to look at foreign links, foreigners say or more reliable. If you can't read English, use Chrome to translate the page.
Back to the Chase,A friend said he ran the program crash Pop-up window: The application is unable to start correctly (0x000007b), because the program does not have source code debugging. OK, Baidu search look. Found a seemingly good link: http://www.tomshardware.com/forum/43092-63-application-unable-start-correctly-0xc000007bThe Final Solution is:
Cause:
the cause of this problem are because of the "Msvcp110.dll" file located at C:\Windows\SysWOW64. This file was used by several applications to run and each has their own version of the file with the same name. So in order run this application, you might replace it with a different msvcp110.dll file which we normally get athttp://www.dll-files.com/
So application might does the next time you try to start it with the below error.
Solution:
Go to C:\Windows\SysWOW64 location and delete the "Msvcp110.dll" file. Now try-to-start the application and the program would generate a new "Msvcp110.dll" file used by the application and your S Hould is able to get the application working Fine
Hope this helps!!
The translation is: the C + + runtime library is missing VS2012. You can download the VS2012 redistributable component in various software tubes at home, and you can run it after the installation is complete.
But, as programmers, we can't just do that. Strictly speaking, when we publish the application, we must see which components the program needs to rely on, and take it with you as needed. Because there is no development environment on the user's computer, it is impossible to have such a specific compiler run-time library.
How do I see what DLLs a program relies on?
This is a very basic skill. In the 1998 release of VC6.0, Microsoft brought a DEPENDS.EXE, the tool is to provide developers to view DLL dependencies. By dragging the EXE and DLL we want to publish, you can clearly see which DLLs the program needs to rely on.
For the system DLL can not be expanded to look at, but the user's own DLL must be expanded to see if it also calls which DLLs, because if this DLL is missing dependent DLLs will inevitably affect the operation of our program. As in, LIBCEF.dll is not a system DLL, we need to see if its DLL is missing, then expand it:
If the DLL is missing, the name of the DLL will turn yellow, as the EXE runs in the absence of the VS2008 c\c++ runtime and Duilib.dll
Then when the program is released, we need to add these DLLs to the EXE path, the user will not encounter any problems.
The application is unable to start correctly (0x000007b) solution