-
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 traces via XHarness #66226
Conversation
Tagging subscribers to 'arch-wasm': @lewing Issue Details
Needs dotnet/xharness#830 to be merged first.
|
- this can be used to symbolicate traces using patterns from `src/mono/wasm/data/wasm-symbol-patterns.txt`. - Includes a wrapper that can be passed to xharness for symbolicating traces in the output. - This can be used as a command line tool also: `dotnet run /path/to/dotnet.js.symbols /path/to/traces` If `-` is passed instead of the last argument, then it reads the messages from stdin.
fd4e890
to
f7e97da
Compare
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
do we still want to take this? |
I think it's useful. |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
Revert unnecessary change
Revert unnecessary change
Revert unnecessary change
The coreclr failure is #70112 . |
src/mono/wasm/symbolicator
project