lwIP - A Lightweight TCP/IP stack - Bugs: bug #56487, [v2.1.2] crash when TCP continuous...
You are not allowed to post comments on this tracker with your current authentication level.
bug #56487: [v2.1.2] crash when TCP continuous write encounter wifi disconnect
Submitter: | Song Pu <pusong666> | ||
Submitted: | Thu 13 Jun 2019 08:19:56 AM UTC | ||
Category: | sockets/netconn | Severity: | 3 - Normal |
Item Group: | Crash Error | Status: | Invalid |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Closed | Planned Release: | None |
lwIP version: | 2.1.1 |
Tue 25 Jun 2019 06:20:00 PM UTC, comment #3: |
Simon Goldschmidt <goldsimon> |
Fri 21 Jun 2019 01:56:56 PM UTC, comment #2: `netif_set_addr()` calls LWIP_ASSERT_CORE_LOCKED(). So this function MUST be called from the Lwip task, not your wifi task.
|
David GIRAULT <dgirault> |
Sat 15 Jun 2019 01:47:28 AM UTC, comment #1: Further explanation:
|
Song Pu <pusong666> |
Thu 13 Jun 2019 08:19:56 AM UTC, original submission:
reproduce ratio:
|
Song Pu <pusong666> |
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 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2019-06-25 | goldsimon | Status | None | Invalid | |
Open/Closed | Open | Closed |
Powered by Savane 3.13-758e.
Corresponding source code
As David already said it, you're doing things wrong. Closing as invalid.