RE: [lwip-users] RE: lwip-users Digest, Vol 14, Issue 9

[Tom C. Barker]

Eric,

I have gotten this issues when I have tried to multi-thread lwIP.
More commonly, I would get it when I would hit a breakpoint on
a thread that accesses lwIP (and is not the lwIp) while my other
threads (lwIP included) run in the background. By design, our 
system does not halt interrupts when we hit a breakpoint.

And, by the way, the solution to the dead-end, multithreaded
implementation of lwIP on our system was to conform to serailized
calls into the lwIP thread via the api's callback message.

Tom

-----Original Message-----
From: address@hidden
[mailto:address@hidden Behalf
Of Leon Woestenberg
Sent: Monday, October 11, 2004 2:19 PM
To: Mailing list for lwIP users
Subject: Re: [lwip-users] RE: lwip-users Digest, Vol 14, Issue 9


Hello Eric,

Eric Shufro wrote:

>Kieran, 
>
>Why would a pcb->next pointer end up pointing to itself (pcb)?
>
>I get infinite loops and cant figure out why. Wonder if it's something with
>the way I call tcpwrite. I create a new pcb, fill in an ip address struct
>and call tcp_connect(...ip addr... callback...) etc..
>
>  
>
Can you enable assert() debugging in some way on your target?

You could sprinkle some assertions like these:

assert(pbuf->next != pbuf);

into often-called positions, then see when it triggers.

Anyway, good luck in debugging.

Regards, Leon.


_______________________________________________
lwip-users mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/lwip-users