RE: [lwip-users] problem in tcp_bind

[Taranowski, Thomas (SWCOE)]

I'm fairly certain there is no concurrency problem, as all communication with 
the core thread goes through the tcpip mailbox.  One interesting tidbit is that 
the crash is always directly preceded by a tcp_close of a socket in the LISTEN 
state.

> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden On
> Behalf Of Jonathan Larmour
> Sent: Friday, March 07, 2008 8:41 AM
> To: Mailing list for lwIP users
> Subject: Re: [lwip-users] problem in tcp_bind
> 
> Taranowski, Thomas (SWCOE) wrote:
> > I'm having a problem with my stack port, where I have some test code
> > that is attempting to bind to a port.  I'm getting an access violation
> > at an unexpected location, and am currently at a loss for what the cause
> > could be.  Any pointers or ideas would be appreciated.  From what it
> > looks like, the list of tcp_listen_pcbs has become corrupted somehow,
> > but I don't know of any likely candidates that would cause this.
> [snip]
> > àif (cpcb->local_port == port) {ß Crashes here
> 
> Thread or interrupt safety issue perhaps? Is there some other timer or
> interrupt context managing to run lwIP core code at the same time?
> 
> As well as, obviously, closing the PCB, the listening PCB list is fiddled
> with in tcp_input() so a new incoming packet filtering up the stack,
> interrupting other lwIP code, is a possibility.
> 
> Jifl
> --
> eCosCentric Limited      http://www.eCosCentric.com/     The eCos experts
>  **  Visit us at ESC Silicon Valley <http://www.embedded.com/esc/sv>  **
>  **  April 15-17 2008, Booth 3012, San Jose McEnery Convention Center **
> Barnwell House, Barnwell Drive, Cambridge, UK.       Tel: +44 1223 245571
> Registered in England and Wales: Reg No 4422071.
> ------["Si fractum non sit, noli id reficere"]------       Opinions==mine
> 
> 
> _______________________________________________
> lwip-users mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/lwip-users