|
From: | address@hidden |
Subject: | Re: [lwip-users] ASSERT-FAIL (invalid message type) |
Date: | Sun, 13 Jan 2019 09:16:51 +0100 |
User-agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 |
Am 12.01.2019 um 14:20 schrieb Norberto R. de Goes Jr.:
Hi all.I have used the lwip stack in my project with multithread, no RAM limitation and running on Linux SO.Does I need to define LWIP_NETCONN_SEM_PER_THREAD parameter (default = 0) ? Is it recommended or mandatory?
It is recommended because it is faster: without it, socket threads create a new semaphore for many calls (to synchronize wih tcpip_thread). By enabling it (and implementing thread-local storage) every thread only creates one semaphore and reuses it many times.
I question that because I am having crash in ".../lwip/src/api/tcpip.c": LWIP_ASSERT("tcpip_thread: invalid message", 0);OBS: msg->type = 2962209658 (invalid)
I don't think this messages is related to LWIP_NETCONN_SEM_PER_THREAD. How do you come to this conclusion?
Regards, Simon
Commits in use (SHA-1) : lwip: c8b65f6c1d2aaa6b3bb1b3d600e54137f294a2d6 lwip-contrib: 4e553f7b3d3af4ac1f3f6c70f38371e4395fdccd Thanks. Norberto Goes -- Norberto R. de Goes Jr. CPqD - DRC Tel.: +55 19 3705-4241 / Fax: +55 19 3705-6125 address@hidden <mailto:address@hidden> www.cpqd.com.br <http://www.cpqd.com.br/> _______________________________________________ lwip-users mailing list address@hidden https://lists.nongnu.org/mailman/listinfo/lwip-users
[Prev in Thread] | Current Thread | [Next in Thread] |