[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #27377] "op_completed" semaphore mechanism crash error
From: |
Simon Goldschmidt |
Subject: |
[lwip-devel] [bug #27377] "op_completed" semaphore mechanism crash error |
Date: |
Mon, 05 Oct 2009 20:00:20 +0000 |
User-agent: |
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; de; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 |
Update of bug #27377 (project lwip):
Status: None => Wont Fix
Assigned to: None => goldsimon
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #5:
I guess what hanhui initially posted is a (potential) bug report that
op_completed might be posted by err_tcp and not checked by another task
afterwards.
However, since op_completed is only posted in states NETCONN_WRITE,
NETCONN_CLOSE and NETCONN_CONNECT, there *is* another task waiting and the
errors he saw are (supposedly) only related to the fact the he used multiple
threads on one netconn, which is not supported (and will not be unless that
API is redesigned).
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?27377>
_______________________________________________
Nachricht geschickt von/durch Savannah
http://savannah.nongnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [lwip-devel] [bug #27377] "op_completed" semaphore mechanism crash error,
Simon Goldschmidt <=