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 native traces from JS, using a symbols file #66042

Merged
merged 10 commits into from
Mar 5, 2022

Conversation

radical
Copy link
Member

@radical radical commented Mar 2, 2022

  • adds support for symbolicating error, and warning messages
  • debug.js.symbols is loaded from the vfs
  • This is enabled by default, only for non-aot tests (since we don't strip aot tests)
  • Works for debugger tests too

@ghost ghost assigned radical Mar 2, 2022
@radical radical added the arch-wasm WebAssembly architecture label Mar 2, 2022
@ghost
Copy link

ghost commented Mar 2, 2022

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

Issue Details

null

Author: radical
Assignees: radical
Labels:

arch-wasm, area-Build-mono

Milestone: -

@radical
Copy link
Member Author

radical commented Mar 2, 2022

/azp run runtime-wasm

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@radical radical force-pushed the symbolicate-from-js branch from 12e529d to 05a1c66 Compare March 2, 2022 19:18
@radical radical requested review from lewing and pavelsavara March 2, 2022 19:18
@radical radical marked this pull request as ready for review March 2, 2022 19:18
@radical radical requested a review from marek-safar as a code owner March 2, 2022 19:18
@pavelsavara
Copy link
Member

In the future we could also add symbols to stack traces which are marshaled as C# exception.
See

@radical radical requested a review from pavelsavara March 2, 2022 20:41
@radical
Copy link
Member Author

radical commented Mar 2, 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 4, 2022

Test failures are unrelated.

@radical
Copy link
Member Author

radical commented Mar 5, 2022

Failures are #66231, and #65817 .

@radical radical merged commit 95770c9 into dotnet:main Mar 5, 2022
@radical radical deleted the symbolicate-from-js branch March 5, 2022 02:38
@ghost ghost locked as resolved and limited conversation to collaborators Apr 4, 2022
@@ -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)
Copy link
Member

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?

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