[wasm][debugger] Fix chinese character in project name

[thaystg]

The test case does not simulate the real case from blazor, but I added it anyway.

From blaze we receive from the loaded_files variable file names like this:
http://localhost:5168/_framework/%E3%84%A8U1U2U3.Shared.dll
Then we need to convert to: http://localhost:5168/_framework/ㄨU1U2U3.Shared.dll to find it in our assemblies by name.

In the debugger-tests in the mono-config.json, the file name is like this, we add and search with this name, so we don't need the UnescapeDataString.

{
      "behavior": "assembly",
      "name": "debugger-test-chinese-char-in-path-\u3128.dll"
}

[ghost]

Tagging subscribers to this area: @thaystg
See info in area-owners.md if you want to be subscribed.

Issue Details

---

The test case does not simulate the real case from blazor, but I added it anyway.

From blaze we receive from the loaded_files variable file names like this:
http://localhost:5168/_framework/%E3%84%A8U1U2U3.Shared.dll
Then we need to convert to: http://localhost:5168/_framework/ㄨU1U2U3.Shared.dll to find it in our assemblies by name.

In the debugger-tests in the mono-config.json, the file name is like this, we add and search with this name, so we don't need the UnescapeDataString.

{
      "behavior": "assembly",
      "name": "debugger-test-chinese-char-in-path-\u3128.dll"
}

Author:	thaystg
Assignees:	-
Labels:	area-Debugger-mono
Milestone:	-

[radical]

nit: unescapedFileName

[radical]

Why is this needed?

[thaystg]

Without this we get an error on CI:

The command ""C:\Users\itomkowicz\source\repos\runtime-fork\.packages\microsoft.diasymreader.pdb2pdb\1.1.0-beta2-19575-01\tools\Pdb2Pdb.exe" "C:\Users\itomkowicz\source\repos\runtime-fork\artifacts\bin\debugger-test\Debug\wasm\debugger-test-special-char-in-path.dll" /out "C:\Users\itomkowicz\source\repos\runtime-fork\artifacts\SymStore\Debug\debugger-test-special-char-in-path\net6.0\x64\debugger-test-special-char-in-path.pdb" /srcsvrvar SRC_INDEX=public" exited with code -1.

[radical]

Any idea what would cause this? And details before that line?

[thaystg]

Pdb2Pdb.exe does not support special characteres in path, as far as I remember.

[radical]

Ok, we can add a comment for that here. And if there is any supporting link with more info, then add that.

[radical]

Can we test this case against other ways of loading assemblies?

• lazy loading
• hot reload

[thaystg]

@lewing Can I backport?

[thaystg]

/backport to release/7.0

[github-actions]

Started backporting to release/7.0: https://github.com/dotnet/runtime/actions/runs/2957101497