@microsoft-github-policy-service agree

I think we can also merge the configuration into enableDWARF: boolean | ModuleConfigurations

sourceMapPathOverrides should work for Node.js just as well as the browser. We don't rely on any special path mapping done by the dwarf module (and I wouldn't really want to add an extra way to map paths) and instead pass the path through the normal path mapping logic (ISourcePathResolver.urlToAbsolutePath)

sourceMapPathOverrides should work for Node.js just as well as the browser. We don't rely on any special path mapping done by the dwarf module (and I wouldn't really want to add an extra way to map paths) and instead pass the path through the normal path mapping logic (ISourcePathResolver.urlToAbsolutePath)

I agree that it's good to keep only one way to map paths. I should appologize for my inaccurate statement:

But it doesn't work when debugging webassembly in nodejs

Let me clarify my issue. There is actually a bug in the C/C++ DevTools Support (DWARF) chrome extension. A temporary solution is adding path substitutions in extension options, so I'd like to do the same thing in vscode.

I have tried to add sourceMapPathOverrides, but after debugging I find that the dwarf symbol url isn't handled by NodeSourcePathResolver.urlToAbsolutePath. So I wonder there are some cases that urlToAbsolutePath can't do but path substitution can when it comes to dwarf symbol resolution.