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

Allow user to manipulate Truffle breakpoints #6866

Merged
merged 1 commit into from
Apr 11, 2024

Conversation

jtulach
Copy link
Contributor

@jtulach jtulach commented Dec 20, 2023

While debugging programs with Truffle based languages it may be useful to disable the Truffle functionality (as it may slow down the debugging a lot - for example running tests on mine graaljs-websocket is quite slow - looks like the VM runs in interpreter only). Currently the only way to disable Truffle breakpoints is to disable the whole module.

This PR offers a different way: It exposes the Truffle breakpoints to the user (under the group Truffle) which can then be disabled as a whole with a single click.

image

What do you think, @entlicher?

Copy link
Contributor

@MartinBalin MartinBalin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like useful feature for polyglots...

@lkishalmi lkishalmi added this to the NB22 milestone Mar 21, 2024
@ebarboni
Copy link
Contributor

will merge this as approved

@ebarboni ebarboni merged commit 393da61 into apache:master Apr 11, 2024
34 checks passed
@mbien
Copy link
Member

mbien commented Apr 11, 2024

the tests here ran the last time in December if i see this correctly. Unfortunately this is breaking master atm.

I am going to prepare a revert PR but let others decide what to do, since many work at a GraalJS update atm so it might have to be coordinated.
image

@mbien
Copy link
Member

mbien commented Apr 11, 2024

-> #7261

@matthiasblaesing
Copy link
Contributor

@jtulach it would be good if you could revisit this. The functionality indeed looks useful, but needs another look (see the necessary revert).

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

Successfully merging this pull request may close these issues.

None yet

8 participants