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

[Kieran Mansley]

On Mon, 11 Oct 2004, Eric Shufro wrote:

> Kieran,
>
> Why would a pcb->next pointer end up pointing to itself (pcb)?

I'm not sure, and without more time to look through it in detail (which I 
don't have at the moment I'm afraid!) can't say anything for certain, but 
problems such as this are often caused by problems with locks or mutexes. 
That would be my first guess.  If you have an environment that lets you 
use tools such as valgrind or gdb, you could try and see what they tell 
you.  gdb in particular would allow you to set a watchpoint on the memory 
location of the "next" pointer so it would stop when it got changed 
and tell you where it was.

Hope that helps, and sorry I don't have enough time to be of more 
assistance.

Kieran