-
Notifications
You must be signed in to change notification settings - Fork 5k
[wasm][debugger] Enable symbolicating traces in Release builds #81172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsCurrently we get:
|
Not for users actually, but for us to debug when users run into runtime crashes. |
I think this is something that @lewing has already discussed with me and it's useful for users also :) |
Feel free to assign it to yourself if you plan to work on it:) |
@radical can you update the status here. |
I haven't had a chance to work on this yet. But we should be able to get to it for 8. |
I will close this issue, as we have already this working using the debugger and also in an exception stack trace. |
case 1
"description": "RuntimeError: memory access out of bounds\n at http://localhost:9400/dotnet.wasm:wasm-function[1020]:0x4de8b\n at http://localhost:9400/dotnet.wasm:wasm-function[1019]:0x4dd09\n at http://localhost:9400/dotnet.wasm:wasm-function[951]:0x49c1f\n at http://localhost:9400/dotnet.wasm:wasm-function[924]:0x48d79\n at http://localhost:9400/dotnet.wasm:wasm-function[247]:0x1a930\n at http://localhost:9400/dotnet.wasm:wasm-function[244]:0x182bc\n at http://localhost:9400/dotnet.wasm:wasm-function[286]:0x1bc9c\n at http://localhost:9400/dotnet.wasm:wasm-function[8318]:0x1b26fc\n at http://localhost:9400/dotnet.wasm:wasm-function[2150]:0x8ebd3\n at http://localhost:9400/dotnet.wasm:wasm-function[2155]:0x8f275"
case 2
The text was updated successfully, but these errors were encountered: