lwIP - A Lightweight TCP/IP stack - Bugs: bug #48416, Problem with nonblocking connect
You are not allowed to post comments on this tracker with your current authentication level.
bug #48416: Problem with nonblocking connect
Submitter: | Christian Prochaska <cproc> | ||
Submitted: | Tue 05 Jul 2016 06:29:25 PM UTC | ||
Category: | sockets/netconn | Severity: | 3 - Normal |
Item Group: | None | Status: | Works For Me |
Privacy: | Public | Assigned to: | goldsimon |
Open/Closed: | Closed | Planned Release: | None |
lwIP version: | git head |
Wed 06 Jul 2016 05:18:18 AM UTC, comment #1: |
Simon Goldschmidt <goldsimon> |
Tue 05 Jul 2016 06:29:25 PM UTC, original submission:
I'm actually not using the most recent version, but from looking at the source code the problem I'm having seems to still exist on the current git master branch (4b136d631af0650247ab1bb21c7eb761d12960b6)
|
Christian Prochaska <cproc> |
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 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2016-07-06 | goldsimon | Status | None | Works For Me | |
Assigned to | None | goldsimon | |||
Open/Closed | Open | Closed |
Powered by Savane 3.13-bb6a.
Corresponding source code
This should work: when LWIP_ERROR is correctly defined to execute "handler", tcp_connect() returns ERR_ISCONN. It does raise an error message by default unless LWIP_NOASSERT is defined to help you finding bugs in your application during development.
If you can't get your application to not behave like this, you can change the LWIP_ERROR define to only execute "handler".