for lwIP users
Subject: Re: [lwip-users] Assertion memp sanity failed at line 463
in../lwip_1_4_0/Src/core/memp.c
I faced with similar problem some time ago. Most likely it means that
global memory was corrupted because of thread-safety problems in your
sys port or freertos configuration or misuse
So you are using FreeRTOS and Cortex-M3 ? I'm 99% sure your interrupt
routine causes problems and I can help you. (I recently faced with very
similar issue).
1. define LWIP_ALLOW_MEM_FREE_FROM_OTHER_CONTEXT to 1 (see description
in src/include/lwip/opt.h). This will let you call safely
Hello
Trying to get LWIP 1.4.1.1 working with FreeRTOS 7.1.1 runs for a while
then gives me the following assertion.
Assertion memp sanity failed at line 463 in
../lwip_1_4_0/Src/core/memp.c
This happens while thrash testing by bulk pinging from a Linux machine
to test capabilities.
Hi,
I had a similar problem recently, and in my case I was first using lwIP
functions from multiple threads (it's not thread safe, don't do that), and then
causing a double free() by calling essentially tcp_close() twice on the same
handle. My guess: you're corrupting memory somewhere,
Hi,
On Fri, Nov 16, 2012 at 10:28:17AM +0100, Mikael Eiman wrote:
Hi,
I had a similar problem recently, and in my case I was first using
lwIP functions from multiple threads (it's not thread safe, don't do
that), and then causing a double free() by calling essentially
tcp_close() twice
I faced with similar problem some time ago. Most likely it means that
global memory was corrupted because of thread-safety problems in your
sys port or freertos configuration or misuse lwip functions from
interrupts. Check sys_arch_protect()/sys_arch_unprotect(),
I noticed that you mentioned LWIP 1.4.1.1 but assertion line shows
lwip_1_4_0. If you use lwip 1.4.0 then be warned that memp sanity check
in that version has error. So if you catch your program looped
indefinitely in memp_sanity function then it still means same problems
(memory corruption).
