Once you have completed these steps, click OK to save the changes and close the Project Options dialog.Ĭ++Builder debug information is stored in. To resolve the problem, enable the Read debug information for statically linked libraries project option in TestComplete. If, for some reason, you cannot turn off the Build with runtime packages option, TestComplete may not be able to get access to the application's internal methods and properties. For more information about runtime packeges, see About Runtime Packages. If this property is unchecked, all information is included in a single executable and can be accessed by TestComplete. TestComplete cannot access debug information in these files and some controls. If this property is checked, C++Builder creates Borland package library (.bpl) files when compiling the application. Select the C++ Compiler | Optimizations category and set the Disable all optimizations option to True: Open your project in CodeGear C++Builder 2009.Ĭhoose Project | Options from the main menu to open the Project Options dialog.
To include debug information into your C++Builder application, follow these steps: Otherwise, you will be unable to access private, protected and public methods and properties of your C++Builder 2009 applications from tests. We recommend that you disable EurekaLog when compiling an application aimed for automated testing with TestComplete. An example of such a tool is EurekaLog 7. Note:ĭebug Info Agent™ is incompatible with tools that change the debug information format. To learn how to prepare applications created with other C++Builder versions, see Implementing Debug Info Agent™ Support in Applications.
This topic explains how to include debug information into applications created with Borland C++Builder 2009.
Debug Info Agent™ exposes public, published, protected and private members of objects in C++Builder applications as soon as the application is compiled with debug information.
0 kommentar(er)
