Re: [lwip-users] tcp_err(...) using problem

[Etienne Lanoy]

Olaf,
This error happen when I call my close_con(..)  function

close_conn(struct tcp_pcb *pcb, struct config_server_ip_tcp_state *es)
{
   tcp_arg(pcb, NULL);
   tcp_sent(pcb, NULL);
   tcp_recv(pcb, NULL);
   if (es)
   {
     if (es->p)
     {
       pbuf_free(es->p);
     }
     mem_free(es);
   }
   tcp_close(pcb);
}

After executing this function, I have my tcp_err(...) which execute itself.

Thanks for your help

Etienne

Olaf Peters a écrit:

> Etienne,
>
> Exactly which error do you get and when (i.e. after which sequence of
> calls)?
>
> Olaf.
>
> -----Original Message-----
>
> Hello everybody,
>
> I'm using raw API interface for a TCP embedded server. I'm using
> lwip standalone (without any OS). Some times my error callback function
> (registered by tcp_err(pcb, my_callback_function)) is called.
>
> I don't understand what's happenend. Anybody know what's kind of events
> can produce this effect ?
>
> I thank you
>
> Etienne
>
>
>
>
> _______________________________________________
> lwip-users mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/lwip-users
>
>
>