Support Board

Date/Time: Fri, 03 May 2024 05:30:43 +0000

Post From: Dynamic Memory Allocation

[2014-03-10 08:58:05] Link To Thread - Link To Post [Go To First Post]
Perseus - Posts: 30
User61322: As I understand it, what you are describing does not sound like an error. There should be no code left to run after "delete" since that statement is in fact the last code executed (see sc.LastCallToFunction). As mentioned above, dynamic allocation seems to be working fine. The CPU exception I am getting is based on something in my DLL (which contains other functions than scsf_DynamicMemoryAllocationExample). A "clean" DLL with only scsf_DynamicMemoryAllocationExample runs without causing an exception.