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

how to debug wasm #1019

Open
fengzikuaipao opened this issue Feb 19, 2025 · 0 comments
Open

how to debug wasm #1019

fengzikuaipao opened this issue Feb 19, 2025 · 0 comments

Comments

@fengzikuaipao
Copy link

fengzikuaipao commented Feb 19, 2025

Hi,I am trying to add a UI plugin for my business and it is necessary to modify trace_processor to support user-defined data;So,I try to debug trace_processor.wasm file in Chrome browser by DevTools, but after add --debug option in run-dev-server script and re-run it,the output trace_processor.wasm.map is empty and the brower cannot recognize it either.
The run-dev-server is modified to the following:

  • $UI_DIR/node $UI_DIR/build.js --serve --watch --debug "$@"

The content of trace_processor.wasm.map is:
{"version":3,"sources":[],"names":[],"mappings":""}

Is debugging wasm files through a browser a suitable way?
What method do you usually use for debugging during development?
Why is the content in the wasm.map file empty?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant