mirror of
https://github.com/RIOT-OS/RIOT.git
synced 2024-12-29 04:50:03 +01:00
11e273c4db
The dark magic used used in thread_measure_stack_free() is frowned upon by valgrind. E.g. valgrind may deduce (by monitoring the stack pointer) that a specific value was at some point allocated on the stack, but has gone out of scope. When that value is now read again to estimate stack usage, it does look a lot like someone passed a pointer to a stack allocated value, and that pointer is referenced after that value has gone out of scope. This is "fixed" by temporarily disabling valgrind error reporting while iterating over the stack. |
||
---|---|---|
.. | ||
include | ||
lib | ||
cond.c | ||
doc.txt | ||
Kconfig | ||
Makefile | ||
mbox.c | ||
msg_bus.c | ||
msg.c | ||
mutex.c | ||
sched.c | ||
thread_flags.c | ||
thread.c |