I have the issue that I sometimes get a data abort exception in the memset function on re-start of my application - the issue however is not the memset function itself but the fact that the linker sometimes places this function directly after the "_ti_sysbios_family_arm_arm9_Cache_wbAll__E" function. However this fuction is missing a return statement at the end and therefore the control flows into the memset function when calling "_ti_sysbios_family_arm_arm9_Cache_wbAll__E". I am using SYS/BIOS 6.33.05.46 and I have created this thread because I do not know whether it is possible to directly create a bug ticket for SYS/BIOS.