lwIP - A Lightweight TCP/IP stack - Bugs: bug #47172, mem.c mem_malloc implementation...
You are not allowed to post comments on this tracker with your current authentication level.
bug #47172: mem.c mem_malloc implementation does not properly account for MEM_ALIGNMENT
Submitter: | David Fernandez <david0fc> | ||
Submitted: | Tue 16 Feb 2016 08:51:06 PM UTC | ||
Category: | None | Severity: | 3 - Normal |
Item Group: | Faulty Behaviour | Status: | Wont Fix |
Privacy: | Public | Assigned to: | goldsimon |
Open/Closed: | Closed | Planned Release: | None |
lwIP version: | git head |
Jump to the original submission
Fri 19 Feb 2016 09:06:50 AM UTC, comment #8: |
Simon Goldschmidt <goldsimon> |
Thu 18 Feb 2016 09:34:06 PM UTC, comment #7: In some hardwares' memory buses, the alignment gap is also read with the data, then thrown away by the cpu.
|
David Fernandez <david0fc> |
Thu 18 Feb 2016 08:43:34 PM UTC, comment #6:
|
Simon Goldschmidt <goldsimon> |
Thu 18 Feb 2016 08:31:33 PM UTC, comment #5:
|
David Fernandez <david0fc> |
Thu 18 Feb 2016 03:11:38 PM UTC, comment #4:
|
Simon Goldschmidt <goldsimon> |
Thu 18 Feb 2016 10:51:59 AM UTC, comment #3:
|
David Fernandez <david0fc> |
Thu 18 Feb 2016 08:28:46 AM UTC, comment #2: I would have thought that both the mem heap and the memp pools go into bss unless you specially tell your linker to put them somewhere else.
|
Simon Goldschmidt <goldsimon> |
Wed 17 Feb 2016 12:14:25 PM UTC, comment #1: Note that memp_memory_xxx seems to suffer of a similar problem.
|
David Fernandez <david0fc> |
Tue 16 Feb 2016 08:51:06 PM UTC, original submission:
The current malloc metadata is defined as:
*/
|
David Fernandez <david0fc> |
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 |
---|---|---|---|---|---|
2016-02-18 | goldsimon | Category | Platform ports | None | |
Status | None | Wont Fix | |||
Assigned to | None | goldsimon | |||
Open/Closed | Open | Closed |
Powered by Savane 3.13-caa5.
Corresponding source code
So your intention is to use a feature for hardware integrity checks to catch programming errors? Sounds a bit odd, but if it works for you, why not. On the other hand, the check is not very safe at it stops checking after using memory once.
Pardon me, but I don't want to add code to lwip for this.
Btw: I do understand the technical reason of the alignment gap. All I said was the C-code is correct - we do not read memory that we don't write before.