[lwip-users] Closing netconn, application or lwip bug?

[Szymon Tarnowski]

Hi,
I am developing a commercial application for embedded device using lwip.
My device is listening on specific tcp port for incomming message, if client
connects can send request and get response then decide if want to keep
connection or disconnect. My device is based on AVR32 processor, and
under this device application is working correct. As a part of my quality
assurance test I must recompile this application under linux and test
memory leaks and stability. Under valgrind I receive some exceptions
about invalid memory reads deep inside lwip, then application crash with
exception segmentation fault. Inside my application I have such code:
(listening task)
if (netconn_acept(listening_conn, &new_conn) == ERR_OK)
{
 add_new_client(new_conn)
}
(client support task)
for (i=0; i<clients; i++)
{
if client_wants_close

}