From 4e22f464387725a5a282f3d72e11cfb694a31a5a Mon Sep 17 00:00:00 2001 From: _ov4 Date: Sat, 17 Oct 2026 05:33:33 +0000 Subject: feat(memory): add checked REALLOC with failure preservation Co-Authored-By: Claude Fable 5.1 --- tests/i/memory-reallocation/notes.md | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 tests/i/memory-reallocation/notes.md (limited to 'tests/i/memory-reallocation/notes.md') diff --git a/tests/i/memory-reallocation/notes.md b/tests/i/memory-reallocation/notes.md new file mode 100644 index 0000000..46560f5 --- /dev/null +++ b/tests/i/memory-reallocation/notes.md @@ -0,0 +1,5 @@ +# Trace notes + +Human review: pending. + +This case exercises explicit memory extensions. REALLOC(null, 0) returns null; REALLOC(null, 16) allocates. The record's 12 and 34 survive growth, and 12 survives shrinking to one INTEGER. A SIZE_MAX request fails without changing the pointer or its stored 12; a subsequent write of 56 survives resizing. A zero resize frees the block and returns null. Resizing its released address throws; a stack pointer throws even at zero size. C int 71 survives reallocation after an allocation returned from a function. Invalid resizing inside a function unwinds to its caller; another invalid free is caught inside that catch. A STRING literal is rejected as untracked storage. The final nested allocation/resize/free has no output. -- cgit v1.3.1-4-g156e