Dirk Vanden Boer
Dirk Vanden Boer
Same issue here using a static build. It immediately asserts on startup when registering a task observer: ``` libc.so.6!__GI_raise(int sig) (raise.c:50) libc.so.6!__GI_abort() (abort.c:79) tbb::detail::r1::assertion_failure_impl(const char * location, int line, const...
This still occurs in release v2021.9.0
> @dirkvdb Could you please check it with current master? Current master also still has the issue
The stack is indeed different, it no longer asserts immediately at startup, it asserts when the parallel_for_each gets executed. ``` #4 0x0000555555d7270a in tbb::detail::r1::assertion_failure_impl (location=0x555557e4d96d "push_front", line=134, expression=0x555557e4d920 "node(val).my_prev_node ==...
One parallel for loop is started. I will try to make a simple reproducer.
I had difficulties reproducing the behavior in a simple test program until I started playing with the linker options. We use cmake and our test executables rely on transitive linking...
The protocol probably changed. I haven't used the code in quite a while
What's your gcc version?
You probably need gcc >= 4.8
Just tested a build on gcc 13.2 without issues