In 2.2 STABLE, tcpip_init <https://github.com/lwip-tcpip/lwip/blob/86c9f7999150199374d7697fd2eed62dcd9b1afa/src/api/tcpip.c#L658-L675> calls lwip_init, which calls netif_init, which calls netif_add for the loopback interface, which asserts LWIP_ASSERT_CORE_LOCKED().
This happens in tcpip_init before it calls sys_mutex_new(&lock_tcpip_core) which initializes the mutex that protects the core. As a consequence, the assertion fails - my question is whether I'm misunderstanding this code? Is the `lock_tcpip_core` mutex not the mutex whose ownership is asserted via LWIP_ASSERT_CORE_LOCKED? - Godmar
_______________________________________________ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
