lwIP - A Lightweight TCP/IP stack - Bugs: bug #37158, MEM_USE_POOLS==1: LWIP_ASSERT...
You are not allowed to post comments on this tracker with your current authentication level.
bug #37158: MEM_USE_POOLS==1: LWIP_ASSERT (rmem == LWIP_MEM_ALIGN(rmem)) fails
Submitter: | Artem Pisarenko <jblackarty> | ||
Submitted: | Tue 21 Aug 2012 01:53:56 PM UTC | ||
Category: | None | Severity: | 3 - Normal |
Item Group: | None | Status: | Duplicate |
Privacy: | Public | Assigned to: | goldsimon |
Open/Closed: | Closed | Planned Release: | None |
lwIP version: | 1.4.0 |
Wed 22 Aug 2012 07:04:47 PM UTC, comment #3: |
Simon Goldschmidt <goldsimon> |
Wed 22 Aug 2012 04:45:54 AM UTC, comment #2: Yes, it's line 134 in my sources too. Seems like debugger interpret sources or places breakpoints in some tricky way.
May be my solution wasn't correct and triggered this issue. But I cannot check without this fix because my lwip port cannot even start without it. |
Artem Pisarenko <jblackarty> |
Tue 21 Aug 2012 02:39:39 PM UTC, comment #1: [Updating the summary to reflect MEM_USE_POOLS==1]
|
Simon Goldschmidt <goldsimon> |
Tue 21 Aug 2012 01:53:56 PM UTC, original submission:
lwip assertion fails at line:
in function mem_free() at mem.c.
Initial data:
lwippools.h:
|
Artem Pisarenko <jblackarty> |
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 5 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2012-08-22 | goldsimon | Status | Need Info | Duplicate | |
Open/Closed | Open | Closed | |||
2012-08-21 | goldsimon | Status | None | Need Info | |
Assigned to | None | goldsimon | |||
Summary | LWIP_ASSERT (rmem == LWIP_MEM_ALIGN(rmem)) fails | MEM_USE_POOLS==1: LWIP_ASSERT (rmem == LWIP_MEM_ALIGN(rmem)) fails |
Powered by Savane 3.13-bb6a.
Corresponding source code
This is a duplicate to bug #33545, already fixed shortly after 1.4.0 was released -> already fixed for 1.4.1.