Hi folks, I've been fuzzing Wasmtime by feeding it sequences of WASI calls. I've encountered a case where Wasmtime would hang > 10 seconds when calling path_open
. I've minimized the call sequence to something like 500 calls. Any suggestion how I can best debug this?
strace? what syscall has it hung on?
Looks like futex.
attach gdb and see a backtrace from there?
Thanks for the pointer! Would I need to run wasmtime debug build for that? Do I need -D debug-info
when invoking wasmtime?
its probably helpful to have a wasmtime debug build, start with that before enabling -D debug-info
even without a debug build the backtrace might give you some clues of where to add some debug prints
Last updated: Dec 23 2024 at 12:05 UTC