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

[GR-60369] JDWP: initialize controller only for the java language. #10268

Closed
wants to merge 1 commit into from

Conversation

graalvmbot
Copy link
Collaborator

Depending on the order between the JDWPInstrument being created and languages being initialized, DebuggerController.onLanguageContextInitialized can be called multiple times (once per language that is initialized after the JDWPInstrument is created).

Typically, the JDWPInstrument is created while espresso is being initialized because JDWPContextImpl#jdwpInit calls env.getInstruments().get(JDWPInstrument.ID) which causes the initialization of the instrument. By that time all other languages are initialized so we don't see an issue.
In a native image with preinitialized contexts though the JDWP instrument might already be created when truffle "replays" the initialization events (e.g., onLanguageContextInitialized) for all languages.

@oracle-contributor-agreement oracle-contributor-agreement bot added the OCA Verified All contributors have signed the Oracle Contributor Agreement. label Dec 9, 2024
@graalvmbot graalvmbot closed this Dec 10, 2024
@graalvmbot graalvmbot deleted the gd/debug-controller-init branch December 10, 2024 10:45
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