lwIP - A Lightweight TCP/IP stack - Bugs: bug #29823, hang when close a connection in...
You are not allowed to post comments on this tracker with your current authentication level.
bug #29823: hang when close a connection in the middle of a communication
Submitter: | juan schiavoni <jjsch> | ||
Submitted: | Fri 07 May 2010 10:27:37 PM UTC | ||
Category: | TCP | Severity: | 1 - Wish |
Item Group: | Crash Error | Status: | Invalid |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Closed | Planned Release: | None |
lwIP version: | CVS Head |
Sat 12 Jun 2010 03:00:34 PM UTC, comment #4: |
Simon Goldschmidt <goldsimon> |
Sat 12 Jun 2010 12:05:52 AM UTC, comment #3: Hi Simon,
|
juan schiavoni <jjsch> |
Wed 19 May 2010 05:27:27 PM UTC, comment #2: Last call for answers: I'll close this as invalid in a few days. |
Simon Goldschmidt <goldsimon> |
Tue 11 May 2010 07:11:59 PM UTC, comment #1: It's pretty difficult to say from here what's wrong. What does "firmware hang" mean? Is it really a "crash error"? If you can say at which line it "hangs", can you debug a bit more? What are other threads doing at that time? Which function is executed? Is the function pointer correct or does it point to an address that doesn't belong to a valid function? |
Simon Goldschmidt <goldsimon> |
Fri 07 May 2010 10:27:37 PM UTC, original submission:
Hi,
|
juan schiavoni <jjsch> |
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 4 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2010-06-12 | goldsimon | Status | Need Info | Invalid | |
Open/Closed | Open | Closed | |||
2010-05-11 | goldsimon | Severity | 3 - Normal | 1 - Wish | |
Status | None | Need Info |
Powered by Savane 3.13-d3ae.
Corresponding source code
Well, thanks for responding so fast ;-)
Anyway, you are using the stack in a way that is not supported: It has been repeated multiple times here and on the mailing lists that using a socket or netconn from 2 threads at a time is not supported!