[EXT_EP-9428] memory allocation functions do not robustly handle case of --heap_size=0 Created: 28/Jul/19 Updated: 25/Oct/23 Resolved: 28/Jul/19 |
|
Status: | Fixed |
Project: | Embedded Software & Tools |
Component/s: | None |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Bug | Priority: | Medium |
Reporter: | TI User | Assignee: | TI User |
Resolution: | Fixed | Votes: | 0 |
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Product: | Code Generation Tools |
Internal ID: | CODEGEN-6501 |
Forum URL: | https://e2e.ti.com/support/development_tools/compiler/f/343/t/579449
https://e2e.ti.com/support/development_tools/compiler/f/343/t/579454 https://e2e.ti.com/support/development_tools/compiler/f/343/t/579456 |
Found In Release: | ARM_18.12.0.LTS PRU_2.4.0* MSP430_18.12.0.LTS ARP32_1.1.0* C2000_18.12.0.LTS |
Fix In Release: | C2000_18.12.4.LTS ARM_18.12.4.LTS PRU_2.4.0* ARP32_1.1.0* MSP430_18.12.4.LTS |
Affected Platform/Device: | default |
Release Notes: | It is possible to set the size of the allocation heap to a total size (such as zero) that is too small to handle any allocations. The C library's dynamic memory allocation routines (e.g. malloc) did not gracefully handle allocations in this case. These functions might crash, or might scribble on unrelated program memory, or might return successfully with a bogus pointer, in which case the caller would likely proceed to write through the bogus pointer and scribble on arbitrary memory. |
Description |
memory allocation functions do not robustly handle case of --heap_size=0 |