Timeline for Is using malloc() and free() a really bad idea on Arduino?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 18, 2023 at 15:07 | history | edited | JRobert | CC BY-SA 4.0 |
Upd to include new-to-me info (in @edgarbonet's comment).
|
| Feb 17, 2023 at 20:28 | comment | added | Edgar Bonet |
@vasilescur: The AVR implementation of malloc()/free() does coalesce adjacent free blocks.
|
|
| Feb 16, 2023 at 23:53 | history | edited | JRobert | CC BY-SA 4.0 |
Upd to respond to a comment.
|
| Feb 16, 2023 at 16:50 | comment | added | vasilescur | I'm curious why the Arduino library's malloc implementation doesn't implement some coalescing of the free blocks like a full OS would. | |
| Jan 16, 2017 at 14:52 | history | edited | JRobert | CC BY-SA 3.0 |
Added static allocation as preferable
|
| Apr 13, 2016 at 5:22 | comment | added | rsaxvc | Another historical note, this quickly led to the BSS segment, which allowed a program to zero its own memory for initialization, without slowly copying the zeros during program load. | |
| Mar 13, 2014 at 12:26 | history | edited | JRobert | CC BY-SA 3.0 |
minor rewording for clarity
|
| Mar 11, 2014 at 16:43 | history | edited | JRobert | CC BY-SA 3.0 |
added 32 characters in body
|
| Mar 11, 2014 at 16:36 | history | answered | JRobert | CC BY-SA 3.0 |