Today I finally captured some debug output. Active debug options: #define SOCKETS_DEBUG LWIP_DBG_ON #define IP_REASS_DEBUG LWIP_DBG_ON #define MEM_DEBUG LWIP_DBG_ON #define MEMP_DEBUG LWIP_DBG_ON #define TCP_DEBUG LWIP_DBG_ON #define TCP_INPUT_DEBUG LWIP_DBG_ON #define TCP_FR_DEBUG LWIP_DBG_ON #define TCP_RTO_DEBUG LWIP_DBG_ON #define TCP_CWND_DEBUG LWIP_DBG_ON #define TCP_WND_DEBUG LWIP_DBG_ON #define TCP_OUTPUT_DEBUG LWIP_DBG_ON #define TCP_RST_DEBUG LWIP_DBG_ON #define TCP_QLEN_DEBUG LWIP_DBG_ON #define TCPIP_DEBUG LWIP_DBG_ON
I dont really know how to interpret these data. Maybe someone more familiar with tcp debug could help me? Maybe that issue is fixed in 1.4.1, as there was some changes in tcp code according to 1.4.1 changelog. I will check it out. On Fri, Feb 22, 2013 at 8:42 PM, Simon Goldschmidt <[email protected]> wrote: > "[email protected]" wrote: > > Perhaps it could be, that there is still a Problem with Bug #24212. > > It has been said, that the Bug has been fixed. I dont really trust in > this. > > A statement like this belongs into the bug tracker or at least in a > suspected bug report on lwip-devel, not into a side-note on lwip-users. > > Unfortunately, I don't have much time for lwIP, lately. If that bug would > be reopened, it would make sure things don't get forgotten. > > Simon > > _______________________________________________ > lwip-users mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/lwip-users > -- 762687 INNOVATION CODE <http://www.762687.com> Tel: +48 783 367 232 Kom: +48 519 136 410 E-mail: [email protected]
lwip_debug.rar
Description: application/rar
_______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
