It turned out to set up the Suppressing option in the BC's setting, such as calling mfc42.dll, the default requirement to try it, then the program exits must release this library, in fact, other programs for Windows should be used, can not be released, this There created so-called memory leaks, and BC also releases these memory since the BC, causing the results that must be rebooted once. Set the Suppressing option to select the Suppressing of all MFC calls, BC has the default division option, and then it is normal.
There are two methods of debugging procedures, one is integrated in the VC, one is separately starting the BC. Let's first say the second case, first, you must use the Open under the File menu to transfer the program that you need to debug, then the Error Suppressing tab appears in the setting below the Program menu, which lists all possible sources related to the program. The program group, each read can be selected separately. After selecting, Suppressing is valid. By default, there is no selected program itself. It should actually select the program itself and other groups. . You carefully take a closer.
In the first case, there is a setting in the menu of the BC, and the content is exactly the same.
Don't worry, each program has its own independent Suppressing settings.
