Home
last modified time | relevance | path

Searched refs:trace (Results 1 – 5 of 5) sorted by relevance

/mbedtls-latest/library/
Dmemory_buffer_alloc.c42 char **trace; member
87 mbedtls_fprintf(stderr, "%s\n", hdr->trace[i]); in debug_header()
282 cur->trace = backtrace_symbols(trace_buffer, trace_cnt); in buffer_alloc_calloc()
304 new->trace = NULL; in buffer_alloc_calloc()
346 cur->trace = backtrace_symbols(trace_buffer, trace_cnt); in buffer_alloc_calloc()
400 free(hdr->trace); in buffer_alloc_free()
401 hdr->trace = NULL; in buffer_alloc_free()
/mbedtls-latest/docs/architecture/
Dpsa-shared-memory.md425 …o use a dynamic instrumentation tool (the most obvious being Valgrind) to trace memory accesses an…
427 …rty that we are looking for. However, it is possible to generate a memory trace with Valgrind usin…
430 valgrind --tool=lackey --trace-mem=yes --log-file=logfile ./myprogram
449 …ry access trace source](https://developer.arm.com/documentation/100964/1123/Plug-ins-for-Fast-Mode…
Dpsa-storage-resilience.md141 * Aborting means removing any trace of the key creation.
/mbedtls-latest/docs/architecture/testing/
Ddriver-interface-test-strategy.md79 * Test that `psa_destroy_key()` does not leave any trace of the key.
/mbedtls-latest/
DChangeLog2749 constant time/constant trace, so side channel attacks can retrieve the