[lwip-devel] [bug #22359] Timing problem with etharp_query()

[Simon Goldschmidt]

Update of bug #22359 (project lwip):

                  Status:                    None => Invalid                
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #2:

The one integral part about lwIP is that its core  isn't protected against
concurrent access. None of the protocols you find in the core dir nor the
etharp implementation may be used from multiple threads (unless protected by
your own implementation). The sys, pbuf and mem functions are an exception,
though.

If you want to use more than one thread, you either have to use one of the
available APIs (socket or netconn) or write your own.

In any case, this is not a bug but an implementation error, so I'm closing it
as invalid.

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?22359>

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.nongnu.org/