tracing: full reset during init
I am using the tracing module using the RAM backend on a system with limited RAM & a buffer that can only store 300ms of tracing data. Current tracing module starts recording during boot-up & we run out of memory prior to executing code we actually want to trace. By reseting buffer metadata here, I can call init() at an arbitrary point of program execution & the tracing module will reset & start tracing. I tested on E2E on an ARM M-class MCU by calling init & then reading buffered tracing data via GDB Signed-off-by: Galen Krulce <gkrulce@meta.com>
This commit is contained in:
parent
023248a1f3
commit
1cfe90d825
|
@ -35,6 +35,8 @@ static void tracing_backend_ram_output(
|
||||||
static void tracing_backend_ram_init(void)
|
static void tracing_backend_ram_init(void)
|
||||||
{
|
{
|
||||||
memset(ram_tracing, 0, CONFIG_RAM_TRACING_BUFFER_SIZE);
|
memset(ram_tracing, 0, CONFIG_RAM_TRACING_BUFFER_SIZE);
|
||||||
|
pos = 0;
|
||||||
|
buffer_full = false;
|
||||||
}
|
}
|
||||||
|
|
||||||
const struct tracing_backend_api tracing_backend_ram_api = {
|
const struct tracing_backend_api tracing_backend_ram_api = {
|
||||||
|
|
Loading…
Reference in a new issue