Covered the trace object registry's name copy and reuse choice

2026-09-16T00:04:48Z

The trace object registry carried three decisions ordinary use never reaches. The name copy stops at the string's terminator, so it never left the loop by its own count; it had no caller that passed no name at all, so the check that recognises one was never true and the line behind it never ran; and the search that reuses an old entry prefers a later free entry to an earlier one unless the earlier one has never held a valid object, which nothing the kernel registers produces. A new regression test creates one object whose name is longer than a registry entry keeps room for and one with no name at all, and asserts the entry each leaves behind. It then fills the registry, registering one entry with the object type the registry treats as not valid, frees that entry last so the search starts there, and registers again - so the search meets a free entry that has never held a valid object and keeps it rather than moving on. The test asserts the new object landed in that entry. The registry is now at 65/65 lines and 42/42 branches, and common/src is at 4339/4339 lines - every line of the certified source is reached in at least one of the six build configurations. Branches are at 4599/4627, up 3 outcomes and the last uncovered line, with the gates raised to 99.95 and 99.30 to hold them. 111/111 tests pass in each of the six. Assisted-by: Claude Code (Opus 5)

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

Covered the trace object registry's name copy and reuse choice