tequ 1ae3fb3f57 fix: record rollback when accept()/rollback() reason is out of bounds (#803) ...

When a hook calls accept() or rollback() with a reason string pointer
outside of wasm memory, HOOK_EXIT returned OUT_OF_BOUNDS and let the hook
keep running. If the hook then returned normally, the execution ended
with exitType UNSET and the HookExecution metadata carried no useful
information about what happened.

Behind the new fixHookExitOutOfBounds amendment, HOOK_EXIT now terminates
the hook as a ROLLBACK with exitCode OUT_OF_BOUNDS (mirroring the guard
violation path), so HookResult and HookReturnCode in the transaction
metadata make the failure visible to hook developers.

Adds a SetHook test covering accept() and rollback() with an out of
bounds reason, with and without the amendment.

Fixes #767

2026-09-25 20:26:59 +10:00

..

Enum.h

Fix comments (#768)

2026-09-01 14:18:28 +10:00

guard_checker.cpp

fix for xahaud codebase

2026-02-20 07:11:14 +09:00

Guard.h

Guard depth 32 (#653)

2026-05-25 11:10:49 +10:00

hook_api.macro

fix for xahaud codebase

2026-02-20 07:11:14 +09:00

Macro.h

fix: record rollback when accept()/rollback() reason is out of bounds (#803)

2026-09-25 20:26:59 +10:00

makefile

fix for xahaud codebase

2026-02-20 07:11:14 +09:00

Misc.h

fix for xahaud codebase

2026-02-20 07:11:14 +09:00

xahau.h

Build xahau.h from source and check in workflow https://github.com/Xahau/xahaud/pull/674

2026-04-28 18:28:59 +10:00