External DWARF debug info

Using this extension I'm trying to debug a wasm binary compiled with external debug info (enabled by the -gseparate-dwarf=<path> and SEPARATE_DWARF_URL options in Emscripten). The only way I've been able to get this to work is by embedding a file: scheme URI to the full path of the dwp file. However this doesn't work with Chrome DevTools and I suspect this is deliberate for security reasons.

Alternative methods I've tried are:

• A relative path to the dwp (works with chrome DevTools)
• A http:// URL to a localhost server serving the dwp (works with chrome DevTools)
• An absolute path

I'd like single approach which works for both the VSCode and Chrome DevTools extensions so the same binary can be debugged in different environments. Is there a way to achieve this?

Start by tracing how the extension handles Emscripten's SEPARATE_DWARF_URL and the dwp URI forms described in the issue. Compare those forms with the paths accepted by Chrome DevTools, including its security constraints, and determine whether one shared URL approach is possible. Done means the same wasm binary can load its external DWARF data in both VS Code and Chrome DevTools.