https://bugs.linaro.org/show_bug.cgi?id=2108
Bug ID: 2108
Summary: lock_main: valgrind
Product: OpenDataPlane - linux- generic reference
Version: 1.7
Hardware: Other
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: ---
Component: General ODP
Assignee: [email protected]
Reporter: [email protected]
With valgrind enabled the test failed make check.
Expected it to be immune to the leak checking or if this is not sensible, then
for "make check" to skip that one case during a valgrind run.
There are however no memory leaks.
odp/test/validation/lock$ valgrind ./lock_main
.....
Suite: nolocking
Test: lock_test_no_lock_functional
...odp_cpumask_task.c:44:odp_cpumask_default_worker():
CPU0 will be used for both control and worker threads,
this will likely have a performance impact on the worker thread.
FAILED
1. lock.c:393 - sync_failures != 0 || global_mem->g_num_threads == 1
2. lock.c:393 - sync_failures != 0 || global_mem->g_num_threads == 1
3. lock.c:393 - sync_failures != 0 || global_mem->g_num_threads == 1
4. lock.c:393 - sync_failures != 0 || global_mem->g_num_threads == 1
5. lock.c:393 - sync_failures != 0 || global_mem->g_num_threads == 1
6. lock.c:393 - sync_failures != 0 || global_mem->g_num_threads == 1
7. lock.c:393 - sync_failures != 0 || global_mem->g_num_threads == 1
8. lock.c:393 - sync_failures != 0 || global_mem->g_num_threads == 1
Suite: spinlock
Test: lock_test_spinlock_api
...odp_cpumask_task.c:44:odp_cpumask_default_worker():
CPU0 will be used for both control and worker threads,
this will likely have a performance impact on the worker thread.
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
lng-odp mailing list
[email protected]
https://lists.linaro.org/mailman/listinfo/lng-odp
