Covered the trace inserts in the tracing machinery's own services

2026-09-15T23:59:33Z

Five in-line trace inserts sit in the trace component itself rather than in a service that uses it: two in the enable, one in the interrupt control, one in each of the two inserts a port's interrupt shim makes around an ISR, and one in the user event insert. Between them they scored four to seven of the twelve branch outcomes the macro carries. A new regression test walks the four ordinary ones once per condition the macro distinguishes: tracing off altogether, thread context with every event enabled, their three event classes filtered out, interrupt context through the test ISR dispatch, initialization context, the state an interrupt presents, and a positioned buffer wrap with and without a buffer-full notification registered. None of these services has an error checking shell in front of it and none refuses a caller on the strength of the system state, so the published entry points reach every insert in every state. The interrupt control is driven as the kernel's own lockout macros drive it, a disable whose returned posture is handed straight back, so the pair is balanced whatever posture it is called in. The buffer is positioned and the service called under one lockout, because the tick's own ISR inserts would otherwise take the boundary. A second test drives the two inserts the enable writes itself. They run a few lines after the buffer pointer and the event enable bits are both set, so the only things left free are the system state, whether the buffer holds a single entry, and what a notification called from inside the first insert does before the second runs. The enable is given a buffer sized from the kernel's own structures to hold exactly one event, with three notifications: one that counts, one that filters the running event's class, and one that turns tracing off - the shape an application capturing a single bufferful of history uses. Four of the five inserts now score twelve of twelve. The user event insert reaches eleven: its own guard on the buffer pointer, a few lines above and inside the same lockout, makes the insert's null arm unreachable. The enable's first insert reaches ten for the same kind of reason - the buffer pointer and the enable bits are assigned above it. Merged over the six build configurations: 4338/4339 lines and 4596/4627 branches, up 36 outcomes, with the branch gate raised to 99.20 to hold them. 110/110 tests pass in each of the six. Assisted-by: Claude Code (Opus 5)

threadx.git/test/tx/regression/threadx_trace_enable_trace_test.c, branch v6.4.1_cert

Covered the trace inserts in the tracing machinery's own services