The current wrapper adds additional allocations that could be avoided with some clever reworking of both krabsetw as well as the flatkrabsetw wrapper. This would include using a thread local arena allocator for pulling out non-primitive data like strings or directly exposing a view of the underlying data that could be copied out by callbacks.

This design is largely in place because it's the lowest barrier to entry wrapping krabsetw. In most cases, it simply results in one or two additional allocations that we could avoid.

Currently we do set an error in krabs_status_ctx on functions that fail but we don't really use the breadth of available error codes. In basically every case, the error is simply set to krabs_error_unknown_error:

Environment
OS Name: Microsoft Windows Server 2019 Datacenter
OS Version: 10.0.17763 N/A Build 17763
Cloud: AWS EC2

Steps to repo

• Installed visual studio community 2019 and Windows 10 SDK (10.0.17763.0).
• Built test_exe.exe successfully.
• Run it on local VM and it was capturing the trace.
• Copied the entire directory (x64/Release) over to another VM with same OS version and run it, the program exited immediately.

Do I need to install any additional package for it to work? Thanks for help!