[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-users] Assertion - tcp_receieve: valid queue length
From: |
Prateek Jain |
Subject: |
[lwip-users] Assertion - tcp_receieve: valid queue length |
Date: |
Fri, 6 Jan 2006 18:16:47 +0530 |
Hello,
I am getting the following assertions.
1.
if (pcb->snd_queuelen != 0) {
LWIP_ASSERT("tcp_receive: valid queue length", pcb->unacked != NULL ||
pcb->unsent != NULL);
}
2.
if (queuelen != 0) {
LWIP_ASSERT("tcp_enqueue: pbufs on queue => at least one queue non-empty",
pcb->unacked != NULL || pcb->unsent != NULL);
}
I couldn't figure out the reason till now.
Based on previous mails on the same topic, I will give some information about my application.
I am writing ftp client which will use PPP. This application will run on ARM with uCos OS.
Iam running three LWIP threads. LWIP version is lwip-1.1.0
1. My FTP CLient App
2. PPP thread.
3. TCPIP Thread.
I have used tcpip_input in netif_add as follows:
if (netif_add(&pc->netif, &pc->addrs.our_ipaddr, &pc->addrs.netmask, &pc->addrs.his_ipaddr, (void *)pd, pppifNetifInit, tcpip_input)) {
Iam using tcp_write API to send the data. This API is called from FTP CLient App context.
I have to send a lot of data ( 150 files of size 20 KB). For every file I open a new connection (tcp_connect) and close it once data goes(tcp_close). This is the way FTP server expects(opening and closing new data conn) -PASV mode
Any inputs will be highly appreciated.
Thanks
Prateek
- [lwip-users] Assertion - tcp_receieve: valid queue length,
Prateek Jain <=