Re: [lwip-devel] queuelen accounting

[patelbaroda]

I have similar problem. I am just running web server and transmitting a large
bmp file/files. There is no task other then web server. With one client
connected, some time, it fires assertion at,

if (pcb->snd_queuelen != 0) {
          LWIP_ASSERT("tcp_receive: valid queue length", pcb->unacked !=
NULL ||
                      pcb->unsent != NULL); in tcp_receive(); // I am not
receiving any thing but transmitting large chunk.

Or

if (queuelen != 0) {
    LWIP_ASSERT("tcp_enqueue: pbufs on queue => at least one queue
non-empty",
      pcb->unacked != NULL || pcb->unsent != NULL);


I read couple of discussion on this issue. I followed the lwip document to
create my web server so if any locking is required, can some body guide me
where to insert locks or any documentation on that?

Thanks





Samuel Thibault-4 wrote:
> 
> Kieran Mansley wrote:
>> As your other problem has potentially raised the issue of multiple
>> threads having concurrent access to lwIP, I think we can probably
>> attribute this error to that.
> 
> Indeed. I had to fix a bunch of other bogus assertions in our code, and
> now it works fine!
> 
> Thanks for lwIP,
> Samuel
> 
> 
> 
> _______________________________________________
> lwip-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/lwip-devel
> 
> 

-- 
View this message in context: 
http://old.nabble.com/queuelen-accounting-tp13384285p26620921.html
Sent from the lwip-devel mailing list archive at Nabble.com.