Editing Object REXX (section)

=== Tracing ===
As in classic Rexx, the <code>TRACE</code> keyword statement and the built-in <code>TRACE()</code> function facilitate debugging. Both allow control over the level of detail and enable interactive debugging at runtime.<ref name=":6">{{Cite book |last1=Flatscher |first1=Rony G. |last2=Winkler |first2=Till |chapter=Devising a TraceObject Class for Improved Runtime Monitoring of ooRexx Applications |date=2024 |title=Proceedings of the 7th ACM International Workshop on Verification and Monitoring at Runtime Execution |chapter-url=https://dl.acm.org/doi/pdf/10.1145/3679008.3685543 |page=19-24|doi=10.1145/3679008.3685543 |isbn=979-8-4007-1119-0 }}</ref> When interactive debugging, the interpreter pauses after most instructions that are traced.<ref name=":2" /> ooRexx 5.1.0 introduces the <code>TraceObject</code> class, which provides additional information such as timestamps, interpreter instances, thread IDs on which messages are dispatched, and the state of the guard locks for tracing multi-threaded programs. This class makes it easier to determine which method is currently guarded and blocked.<ref name=":6" />

The ooRexx debugger, which is also included in the "net-oo-rexx" bundle, is based on Trace and offers a [[graphical user interface]] (GUI) that uses the [[Object REXX#Java|Java bridge]] to facilitate debugging on all platforms.<ref name=":12" /><ref>{{Cite web |date=2025-01-26 |title=ooRexx Debugger |url=https://sourceforge.net/projects/oorexxdebugger/ |access-date=2025-02-02 |website=SourceForge |language=en}}</ref>