lwIP - A Lightweight TCP/IP stack - Bugs: bug #63435, Timer allocation fails are silent
You are not allowed to post comments on this tracker with your current authentication level.
bug #63435: Timer allocation fails are silent
Submitter: | Engin Aydogan <engin> | ||
Submitted: | Mon 28 Nov 2022 01:07:26 PM UTC | ||
Category: | TCP | Severity: | 3 - Normal |
Item Group: | Faulty Behaviour | Status: | Works For Me |
Privacy: | Public | Assigned to: | goldsimon |
Open/Closed: | Closed | Planned Release: | None |
lwIP version: | 2.1.3 |
Wed 11 Oct 2023 07:44:32 PM UTC, comment #1: |
Simon Goldschmidt <goldsimon> |
Mon 28 Nov 2022 01:07:26 PM UTC, original submission:
Hello, why is this error silent? When this allocation fails, TCP stack does not do retransmissions and I think it's a serious problem.
*/
|
Engin Aydogan <engin> |
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 |
---|---|---|---|---|---|
2023-10-11 | goldsimon | Status | None | Works For Me | |
Assigned to | None | goldsimon | |||
Open/Closed | Open | Closed |
Powered by Savane 3.13-d3ae.
Corresponding source code
I'm not sure what the problem is. Looking at sys_timeout_abs(), there's an LWIP_ASSERT() that should trigger an abort when timeout allocation fails. Of course, you can chose to disable that by setting LWIP_NOASSERT=1, but that's not a wise thing to do, is it?