Skip to content
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

Merged
merged 21 commits into from
Jun 2, 2022

Conversation

radical
Copy link
Member

@radical radical commented Mar 5, 2022

  • adds a new src/mono/wasm/symbolicator project
    • which can be used as a standalone command line tool to symbolicate traces manually
    • has a wrapper that can be passed to xharness, to symbolicate automatically

@radical radical added arch-wasm WebAssembly architecture area-Build-mono labels Mar 5, 2022
@ghost ghost assigned radical Mar 5, 2022
@ghost
Copy link

ghost commented Mar 5, 2022

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details
  • adds a new src/mono/wasm/symbolicator project
    • which can be used as a standalone command line tool to symbolicate traces manually
    • has a wrapper that can be passed to xharness, to symbolicate automatically

Needs dotnet/xharness#830 to be merged first.
Based on #66042

Author: radical
Assignees: -
Labels:

arch-wasm, area-Build-mono

Milestone: -

radical added 5 commits March 4, 2022 21:40
- 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.
@radical radical force-pushed the symbolicate-xharness branch from fd4e890 to f7e97da Compare March 5, 2022 02:41
@radical radical requested a review from lewing March 10, 2022 20:29
@radical radical marked this pull request as ready for review March 10, 2022 20:29
@radical radical requested a review from marek-safar as a code owner March 10, 2022 20:29
@radical
Copy link
Member Author

radical commented Mar 10, 2022

/azp run runtime-wasm

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@radical
Copy link
Member Author

radical commented Mar 11, 2022

/azp run runtime-wasm

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@lewing
Copy link
Member

lewing commented May 17, 2022

do we still want to take this?

@radical
Copy link
Member Author

radical commented May 17, 2022

I think it's useful.

@lewing lewing requested a review from maraf May 17, 2022 19:15
@radical
Copy link
Member Author

radical commented May 25, 2022

/azp run runtime-wasm

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@radical
Copy link
Member Author

radical commented May 25, 2022

/azp run runtime-wasm

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@radical
Copy link
Member Author

radical commented May 25, 2022

/azp run runtime-wasm

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@radical
Copy link
Member Author

radical commented May 26, 2022

/azp run runtime-wasm

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@radical
Copy link
Member Author

radical commented May 27, 2022

/azp run runtime-wasm

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@radical
Copy link
Member Author

radical commented May 28, 2022

/azp run runtime-wasm

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@radical
Copy link
Member Author

radical commented May 31, 2022

/azp run runtime-wasm

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

radical added 3 commits May 31, 2022 19:34
Revert unnecessary change
Revert unnecessary change
Revert unnecessary change
@radical
Copy link
Member Author

radical commented Jun 1, 2022

The coreclr failure is #70112 .

@radical radical merged commit 104013a into dotnet:main Jun 2, 2022
@radical radical deleted the symbolicate-xharness branch June 2, 2022 01:59
@ghost ghost locked as resolved and limited conversation to collaborators Jul 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
arch-wasm WebAssembly architecture area-Build-mono
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants