日本ローターバッハ Official site

AI-assisted debugging has finally arrived!

The debugging work using AI as envisioned by Rothbarth.

We will introduce "The Three Steps of Debugging with AI" as conceived by Roterbach, along with "The Specific Roles and Limitations of AI." In AI-assisted debugging, AI assists engineers in analysis and judgment through the following framework. "The Three Steps of Debugging with AI" 1. Source Code (Hypothesis) This shows what the system is "supposed to do (intent and logic)." 2. Execution Trace (Evidence) This presents objective data on what the system "actually did (timing and state changes)." 3. AI (Interpretation) This connects the code (context) and the trace (evidence), accelerating the analysis and insights into patterns and possible root causes. When problems arise, it is common to unexpectedly spend a significant amount of time analyzing logs or reviewing code for root cause investigation. Identifying the cause requires checking and eliminating each possibility one by one.

Related Link - https://jp.lauterbach.com/

basic information

"The Specific Roles and Limitations of AI" AI is greatly helpful in the aspect of "cause investigation." What AI excels at is quickly accessing necessary information from vast documents such as manuals, specifications, and register descriptions, as well as finding patterns within complex system data and logs to suggest possible causes. Much of the debugging time is spent not on "executing code" but on "searching for information," so reducing this friction is the true value of AI. "Limitations of AI to Remember" AI cannot make judgments without execution data (evidence). AI infers based on the given context and evidence (logs and trace data). If data is insufficient, it cannot accurately determine what actually happened. It does not replace the judgment of engineers. The final decision-making regarding investigation policies and judgments must still be carried out by the engineers themselves. AI is not a magical tool; by utilizing it as a means for "quick access to relevant knowledge" and as an "assistant to help interpret evidence," it significantly enhances the productivity of debugging tasks.

Price range

Delivery Time

Model number/Brand name

TRACE32

Applications/Examples of results

This feature is a new functionality released in November 2026. For more details, please contact us.

TRACE32 Solution Overview

CATALOG

TRACE32 Tricore AURIX Compatible Debugging & Tracing Tool

PRODUCT

TRACE32 ARM-compatible Debugging & Tracing Tool

PRODUCT

ARM CORTEX-M compatible fastest debugging and tracing tool

PRODUCT

Explained in Manga! Solve both debugging and tracing with one device! μTrace

TECHNICAL

Recommended products

Distributors

At Japan Rotalbach, we sell and support various embedded software development tools under the name TRACE32, including hardware debugger solutions, debugging software, trace devices, and simulators.