Build the debug configuration of the project and ensure it crashes.This will trigger a stack overflow unless the bigvar variable is optimized out. Start the Keil uVision IDE and create an RTX-based project with the following code in one of the thread functions:.We will then compare the 2 versions of the project, showing how to quickly locate the differences between them and to adjust the settings accordingly.īefore you begin, install VisualGDB 5.4 or later.include search path and preprocessor macros), but will preserve the default optimization settings, triggering the stack overflow. This will handle the source files and common settings (e.g. Import the project into VisualGDB using the basic Keil importing plugin.Override the optimization in Keil project properties.Create a project with the Keil uVision IDE that will trigger a stack overflow unless full optimization is used.In this tutorial we will do the following: However, sometimes, overridden values of rarely used settings can trigger behavior difference between the projects built with VisualGDB and other IDEs and this tutorial provides detailed steps on diagnosing such differences. Normally, the steps described in this tutorial are not needed because VisualGDB can automatically import commonly used settings from most popular project formats. This tutorial shows how to diagnose problems in projects imported into VisualGDB from other IDEs by comparing the command lines used to build the projects with VisualGDB and in the other IDE.
0 kommentar(er)
