in theory wasp could be debuggable inside chrome https://developer.chrome.com/blog/wasm-debugging-2020/

wasm tool conventions

https://github.com/WebAssembly/tool-conventions

dwarf

custom sections contain dwarf in binary format which can be translated to text using llvm-dwarfdump

.debug_info .debug_loc .debug_ranges .debug_abbrev .debug_line
.debug_str 0-terminted strings

source map

{"version":3,"sources":["source.wasp""],"names":[],"mappings":"qeAOA,…"}

the parser is available here:

https://github.com/bmeurer/wasm-source-map

WASM_LINKFORSHARED_DEBUG="-gseparate-dwarf --emit-symbol-map"