Safety-certified tools Tools for Automotive Applications C-STAT Static analysis C-RUN Runtime analysis Debugging and trace probes
C-RUN helps you find errors at an early stage. It is completely integrated with IAR Embedded Workbench and provides detailed runtime error information.
C-RUN is developed in house by compiler and debugger experts and has a wide range of features based on customer requests and research in developer needs.
Make runtime analysis a natural part of your day-to-day workflow! No additional applications or integrations are needed. Simply select the desired checks, rebuild the project and run it in the debugger.
C-RUN performs runtime analysis by checking application execution directly within the development environment. It checks for arithmetic issues, bounds issues and heap integrity and will tell you what went wrong and where.
What is Runtime Analysis?
By inserting test code into an application, a runtime analysis tool can find real and potential errors in the code while executing the program in a software debugger.
What is a typical error that can be detected with runtime analysis?
Out of bounds, arithmetical errors and memory inconsistency errors.
Why do I need Runtime Analysis?
By using runtime analysis, you can find potential and real errors at an early stage, as opposed to finding errors at a later stage which makes product development more expensive and time consuming. It improves cost efficiency and development time, allowing for a speedier time to market.
Does C-RUN support both C and C++?
Can I use C-RUN in C-SPY simulator? And in my actual target hardware?
Yes and Yes
How can I evaluate C-RUN?
A size-limited version of C-RUN is activated for evaluation when you download IAR Embedded Workbench for Arm V7.20 (and later versions) or IAR Embedded Workbench for RX V3.10. Note that the KickStart (size-limited) and Baseline editions of IAR Embedded Workbench does not work with C-RUN.
Which Arm cores does C-RUN support?
All supported cores in IAR Embedded Workbench for Arm.
Is there any feature limitation of C-RUN evaluation?
Demo of how to work with integrated code analysis in IAR Embedded Workbench for Arm.