lwIP - A Lightweight TCP/IP stack - Bugs: bug #31748, Calling non-blocking connect more...
You are not allowed to post comments on this tracker with your current authentication level.
bug #31748: Calling non-blocking connect more than once can render a socket useless
Submitter: | Yoav <djinng> | ||
Submitted: | Thu 02 Dec 2010 01:49:40 PM UTC | ||
Category: | sockets/netconn | Severity: | 3 - Normal |
Item Group: | Faulty Behaviour | Status: | Fixed |
Privacy: | Public | Assigned to: | goldsimon |
Open/Closed: | Closed | Planned Release: | None |
lwIP version: | CVS Head |
Mon 14 Mar 2011 09:27:16 PM UTC, comment #3: |
Simon Goldschmidt <goldsimon> |
Mon 14 Mar 2011 09:01:59 PM UTC, comment #2: 3. and 4. are fixed: ERR_ISCONN now translates to EALREADY (since it is only used in this case now). |
Simon Goldschmidt <goldsimon> |
Mon 24 Jan 2011 07:33:48 PM UTC, comment #1: 3. is correct: EALREADY should be returned. The only problem is we currently have an err_t representation for this, so it seems we need to add one. |
Simon Goldschmidt <goldsimon> |
Thu 02 Dec 2010 01:49:40 PM UTC, original submission:
If connect is called again while a previous non-blocking connect is being processed, ERR_ISCONN is assigned to conn->err.
|
Yoav <djinng> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 5 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2011-03-14 | goldsimon | Status | In Progress | Fixed | |
Open/Closed | Open | Closed | |||
2011-03-14 | goldsimon | Assigned to | None | goldsimon | |
2011-03-14 | goldsimon | Status | None | In Progress | |
2011-01-11 | kieranm | Planned Release | 1.4.1 |
Powered by Savane 3.13-02a9.
Corresponding source code
Sorry messing with the planned release, but I just had to fix this since it mainly involves changing "FATAL" classification of error codes: ERR_USE and ERR_ISCONN just aren't fatal to me.