Skip to content

[GR-62872] WebAssembly debugger fixes and extensions. #11073

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

Open
wants to merge 10 commits into
base: master
Choose a base branch
from

Conversation

graalvmbot
Copy link
Collaborator

No description provided.

Lines are no longer looked up based on the function offset, but in the entire range of possible bcis in a function.
Simplified reading of entries in the DebugParser and DebugTranslator.
Fixed bug, where functions that are no longer in the binary would lead to incorrect debug line mappings.
Introduced WasmFunctionBaseNode to support replacement of instrumentable nodes in wasm.
Now replaces the WasmFunctionNode when an instrument attaches instead of rewritting the bytecode of the existing one.
Made WasmInstrumentationSupportNode PE friendly.

# Conflicts:
#	wasm/src/org.graalvm.wasm/src/org/graalvm/wasm/nodes/WasmFixedMemoryImplFunctionNode.java
#	wasm/src/org.graalvm.wasm/src/org/graalvm/wasm/nodes/WasmInstrumentableFunctionNode.java
… debug function.

The line number program now uses correct file paths.
Debug sources now use the full path instead of the file name.
Inner contexts now get the io access and polyglot access privileges from their outer context.

The mapping of debug source offsets to lines is now represented by line indices instead of lines. This allows for a more compact representation and easier lookup.
Debugger can now modify wasm values.
Fixed a bug where values in the dwarf debugging format were interpreted as signed instead of unsigned.
Debug sources are no longer loaded by wasm. The debugger is now responsible for loading the relevant files.
Added support for wasm files when connected to a chrome debugger.
Corrected documentation.
DebugArrayDisplayValue and DebugObjectDisplayValue now share ExportMessage implementation.
…t at debug source file.

Fixed a potential NPE bug when checking for wasm mime type.
No longer materialize instrumentable nodes that do not point to existing files.
Introduces a test mode for the debugger tests.
@oracle-contributor-agreement oracle-contributor-agreement bot added the OCA Verified All contributors have signed the Oracle Contributor Agreement. label Apr 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OCA Verified All contributors have signed the Oracle Contributor Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants