-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[wasm] Add support for symbolicating native traces from JS, using a symbols file #66042
Conversation
Tagging subscribers to 'arch-wasm': @lewing Issue Detailsnull
|
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
.. warnings. The regex patterns are hardcoded in `debug.ts`. And the symbols are loaded from `dotnet.js.symbols`. We try to symbolicate wherever possible.
12e529d
to
05a1c66
Compare
In the future we could also add symbols to stack traces which are marshaled as C# exception. runtime/src/mono/wasm/runtime/method-calls.ts Line 459 in 842f4d7
|
.. and use that to symbolicate traces marshaled as C# exceptions (thanks to @pavelsavara for the suggestion).
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
Test failures are unrelated. |
@@ -39,7 +39,7 @@ run-browser: | |||
fi | |||
|
|||
run-console: | |||
cd bin/$(CONFIG)/AppBundle && $(V8_PATH) --stack-trace-limit=1000 --single-threaded --expose_wasm $(MAIN_JS) -- $(DOTNET_MONO_LOG_LEVEL) --run $(CONSOLE_DLL) $(ARGS) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This broke browser-bench's make run
for console version. Why was --run $(CONSOLE_DLL)
removed? Do I need to update browser-bench's Makefile somehow?
debug.js.symbols
is loaded from the vfs