In Series 60 SDK, you can use two versions of the simulator executable: A version contains symbol debugging information, the other is a release version. The release simulator is limited to only evaluate or demonstrate applications - it starts very fast because it does not have debugging information. Both versions are called EPOC.EXE, but they are located in their own subdirectory. EPOC This name is historically legacy - it is the name of the operating system before the Symbian OS. In normal development activities, the simulator's debugging form is often used. Depending on your choice IDE, you can use the debug version or use debug versions in "Debug Mode". It is a bit confusing to run the same "debug simulator" in both modes. Sometimes you might want to start the simulator, locate the application and run it, and this is just for the purpose of testing. If a serious error occurs, the simulator and the application will be closed in a constraint. Also, you may want to set breakpoints (in code) that you think there is a problem (code), then let the IDE run the simulator in the Debug mode. Then you locate the application and run it. Applicable to the application will encounter breakpoints in the code. On the breakpoint, the source code will appear in the IDE and simultaneously display all symbol debug information related to the application. Next, you can debug the code snippet step by step by step by step by step by controlling. You can view the application source code, data, data, call stack, and other information related to debug-related information to help you track the errors in code or logic. Figure 1-3. Series 60 Platform 1.2 Debugging Simulator Application Form and List View Chart 1-4. Microsoft Visual C IDE is in debug mode HelloWorld application simulator executable file location Series 60 1.2 SDK Release Simulator Typically located below: For Visual C /Symbian/6.1/series60/epoc32/Release/Wins/urel/epoc.exe for Borland C /Symbian/6.1/series60/epoc32/Release/Winsb/urel/epoc.exe For codewarrior /symbian/6.1/series60/epoc32/release/winscw/urel/epoc.exe debugging emulators typically located: for Visual C /symbian/6.1/series60/epoc32/Release/Wins/udeb/epoc.exe For Borland C /Symbian/6.1/series60/epoc32/Release/winsb/udeb/epoc.exe For code, the accurate path is depends on your installation SDK in the installation of Code, DINSC32/Release/Winscw/udeb/epoc.exe When choosing the option. The path to the simulator in Series 60 2.x SDK will be very similar -, for example, /symbian/series602_0/epoc32/Release/wins/udeb/epoc.exe. Figure 1-3 shows the Series 60 1.2 simulator. When it starts, the application main menu is displayed as a table view or list view. SERIES 60 2.0 Simulator Started profile similar phone application, you must navigate to the application menu by pressing the application button shown in Figure 1-3. Regardless of which version of the Series 60 platform, the debugging (UDEB) version of the simulator executable is generally used as the default option for the development project - for example /Epoc32/Release/wins/udeb/epoc.exe.
When the simulator debug mode runs the application in the debug mode of the simulator, the source code, the function call stack, and variable information, etc., will be displayed immediately when the code breakpoint is encountered, as shown in Figure 1-4. If the application code is not in a position that requires a user input, the simulator window itself may disappear (it is minimized). Run the simulator from the command prompt If you need to run the debug simulator from the command line, you only need to open the command prompt, change the current path to the Series 60 SDK folder where the EPOC.EXE application is located (such as /symbian/6.1/series60/ EPOC32 / RELEASE / WINS / UDEB) and enter the following: The command above the EPOC will start the debug simulator, then you can locate and run your own application, but it is not in debug mode. To make the debugged application run in the debug mode of the simulator, you can only complete it from the IDE. If you want to run the publishing simulator, you need to enter: EPOC -REL runs the emulator in Visual C IDE in Visual C IDE you press CTRL F5 or from the menu to select Build | EPECUTE EPOC.EXE to start the simulator Debug version. This will enable the simulator in a non-debug mode. Instead, press F5 or from the menu to select Build | START DEBUG | GO will enable the simulator to debug mode. When you first run a simulator of a Visual C project, a dialog box will ask you the name of the executable. Please navigate to the EPOC.exe file of the / EPOC32 / RELEASE / WINS / UDEB folder for the root directory of the SDK. Run an emulator in Borland C Builder 6 and C Builderx IDE You can use the Tools | Mobile Build Tools menu option to select Run Emulator to launch the debug version of the simulator. Or use the Run | Run menu option (F9), but it will cause the project to re-establish each time - and this cost can be very long. When using this option, you may need to terminate the establishment dialog ("Compiling") before the simulator starts. If you run the simulator in C Builder, use the Run | Debug Project menu option or press SHIFT F9. If you want to re-establish the project and start the simulator, select Run | Run Project or press F9. Run the emulator in the CodeWarrior IDE Select the Project | Run menu option or press the Ctrl F5 to run the simulator. Press F5 or use the Project | Debug menu option to make the simulator run in debug mode. Positioning and running the application by clicking the image of the cursor key on the mam sign bitmap, or using the PC keyboard cursor (arrow) key to select the HelloWorld application. Click the "Selection" button (in the middle of the cursor control button) to start the application. Note that there is no specific icon (specified in the .aif file) will be given a default icon, which looks like a serrated platter. In some SDK / IDEs (such as some versions of Borland and CodeWarrior), your created app may be located under the "Other" folder without being on the home desktop. If this happens, navigate and select the Other folder, then open it by clicking the "Selection" button. Navigate and select the HelloWorld application and click the "Selection" button to call the application.
Figure 1-5. "HelloWorld" application debugging application is replaced, you can make the application running on the simulator in the IDE to debug mode - this process verification relies on the IDE used. Typically, you need to set breakpoints first on the appropriate position of the source code. Start the simulator in debug mode. Since the application is to be debugged (essentially dynamic link library DLL), instead of the simulator itself, you need to navigate and run the application. The app will start and execute when you set the breakpoint you set. Then you can use your own IDE tool to gradually execute the source code for the application. More IDE helps this article does not have more descriptions of different IDE features, so if you want to query more IDE help information, you can do it through the Help menu option. For Microsoft Visual C , you can choose the Help | Contents menu option, which is provided in the MSDN installed with the IDE. For Borland C Builder 6, you can use the Help menu option. You will find an independent Help | Borland C Mobile Edition Help page except for the standard Borland help file. For C Builderx, you can choose Help | Help Topics, then select Mobile Development. For Metrowerks CodeWarrior, there is a Help | Online Manuals menu option, which contains a lot of valuable information when using Symbian OS. More specific IDE information can be obtained online, for example, to http://msdn.microsoft.com/ link find Visual C information, to http://bdn.borland.com/ link to find Borland C information, to HTTP : //www.metro-wireks.com/mw/develop/wireless/ Link Find CodeWarrior Information. Article Source: http://symbian.org.cn/bbs/viewtopic.php? T = 868
