Timeline for AVR - How to know that there is collision between stack and heap or the memory has filled?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 19, 2017 at 12:44 | vote | accept | Ahmad Naoum | ||
| Feb 1, 2016 at 14:45 | comment | added | Mikael Patel | @EdgarBonet I seem to have missed one of the requirements; software with dynamic configuration, e.g. EEPROM variables that say number of elements, etc. The actual size of the dynamic data structure is not known at compile time or is allowed to change. In other cases, I fully agree with your objection. If the size is known avoid malloc(). | |
| Feb 1, 2016 at 14:30 | comment | added | Edgar Bonet | "allocate memory with malloc() during the setup()". If you know from the very beginning how much memory you need, there is no point in using malloc() instead of static buffers. As to what usages of malloc() are safe, see my answer to a related question. | |
| Feb 1, 2016 at 10:51 | history | edited | Mikael Patel | CC BY-SA 3.0 |
added 80 characters in body
|
| Jan 30, 2016 at 21:28 | history | answered | Mikael Patel | CC BY-SA 3.0 |