dangernoodle-io / breadboard / 30733066031

97%

push

github

feat: add bb_task stack high-water-mark accessor (#1198)

bb_task_stack_hwm_bytes(handle_or_null) is a live pull -- queries
uxTaskGetStackHighWaterMark() on demand, distinct from the base
registry's existing free_bytes field (a periodic-scan cached push).
NULL means the calling task, matching FreeRTOS's own
uxTaskGetStackHighWaterMark(NULL) semantics and bb_wdt's existing
bb_wdt_task_subscribe_handle(NULL) idiom.

Unit normalization: uxTaskGetStackHighWaterMark() returns WORDS, not
bytes -- the espidf shell converts via the existing
bb_num_words_to_bytes() SSOT (B1-1256), the same helper the base
registry's periodic scan already uses, rather than hand-rolling a
second * sizeof(StackType_t) multiply.

Kconfig: no guard added. uxTaskGetStackHighWaterMark() depends only
on INCLUDE_uxTaskGetStackHighWaterMark -- the public function's own
gate is a single condition, #if (INCLUDE_uxTaskGetStackHighWaterMark ==
1). (The OR condition gating configUSE_TRACE_FACILITY OR
INCLUDE_uxTaskGetStackHighWaterMark governs the internal helper
prvTaskCheckFreeStackSpace() that uxTaskGetStackHighWaterMark() calls,
not the public function itself.) ESP-IDF's FreeRTOSConfig.h
(components/freertos/config/include/freertos/FreeRTOSConfig.h)
hardcodes INCLUDE_uxTaskGetStackHighWaterMark to 1 unconditionally on
every target this repo builds for, and this FreeRTOSConfig.h is shared
across xtensa and riscv ports. CONFIG_FREERTOS_USE_TRACE_FACILITY
(tracked by B1-1261/B1-1296) gates uxTaskGetSystemState() only, not
this one -- that distinction is why the base scan's guard differs from
this function's lack of one.

Host stub: no real FreeRTOS stack to measure, so it never fabricates
a plausible-looking number -- returns a test-injectable value only
(bb_task_test_set_stack_hwm_bytes(), BB_TASK_TESTING build),
defaulting to 0.

B1-1365


Claude-Session: https://claude.ai/code/session_0119nuE2NZME9y2aYEVJTPB5

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

8220 of 8784 branches covered (93.58%)

Branch coverage included in aggregate %.

8 of 8 new or added lines in 1 file covered. (100.0%)

13914 of 14069 relevant lines covered (98.9%)

2602.89 hits per line