Skip to main content

How can GUI operations performed in TRACE32 PowerView be saved as a CMM script? - Knowledgebase / TRACE32 PowerView - Lauterbach Support

How can GUI operations performed in TRACE32 PowerView be saved as a CMM script?

Authors list

If you have manually configured TRACE32 PowerView through the graphical user interface and want to reproduce the same sequence of actions later, you can record the GUI operations with the LOG command group. The recorded commands are written to a PRACTICE (*.cmm) script.

Example:

; ============================================
; TRACE32 GUI operation logging
; ============================================
; Open log file
LOG.OPEN ~/myDebugLog.cmm
; Start logging
LOG.ON
; ============================================
; Perform operations in TRACE32:
;
; - Click menu items
; - Open windows
; - Set breakpoints
; - Run the program
; - View variables
; - etc.
; ============================================
; Stop logging
LOG.OFF
; Close the log file
LOG.CLOSE

The generated myDebugLog.cmm file can serve as a starting point for automating your workflow with PRACTICE scripts. Depending on your use case, you may want to review and simplify the recorded commands before using the script in production.

This feature is particularly useful for learning the corresponding PRACTICE commands for GUI operations or for quickly creating an initial automation script from an interactive debugging session.

Helpful Unhelpful

Add a comment

ID-0
To prove you are a human, please tell us the text you see in the CAPTCHA image