[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #48416] Problem with nonblocking connect
|
From: |
Simon Goldschmidt |
|
Subject: |
[lwip-devel] [bug #48416] Problem with nonblocking connect |
|
Date: |
Wed, 6 Jul 2016 05:18:18 +0000 (UTC) |
|
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36 |
Update of bug #48416 (project lwip):
Status: None => Works For Me
Assigned to: None => goldsimon
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #1:
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".
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?48416>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/