Skip to content

graalpy can not set breakpoints #900

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

Closed
EricCD-S opened this issue Mar 31, 2025 · 7 comments
Closed

graalpy can not set breakpoints #900

EricCD-S opened this issue Mar 31, 2025 · 7 comments

Comments

@EricCD-S
Copy link

Hi, I've recently been trying to build a debugging client using graalpy as an adapter, and most of the functionality works fine, but the request "setBreakpoints" doesn't work. At the end of the running will get "[Graal DAP] Error: null". May I ask how you guys solved this problem while writing the code? Thanks

@kaisalmen
Copy link
Collaborator

Hi @EricCD-S I don't remember seeing this particular issue, but it also was early this year. You don't see this problem in our example or do you?

@EricCD-S
Copy link
Author

EricCD-S commented Apr 3, 2025

#842
I find this merge history and the problem I meet seems very similar to this one. Graalpy can not hit breakpoint and get "[Graal DAP] Error: null" when program finish. So I am thinking the same problem may have already been solved?

@EricCD-S
Copy link
Author

EricCD-S commented Apr 3, 2025

I tried change file path format. But it doesn't work.

@kaisalmen
Copy link
Collaborator

Hi @EricCD-S a I forgot about this one:
It is this commit 36687a7 The paths weren't the same. Even if created unix style on the client side the paths come back with backslashes on Windows. 🤷‍♂ Therefore I introduced this "hack" in the referenced commit.

@EricCD-S
Copy link
Author

EricCD-S commented Apr 3, 2025

I tried different path format, but this question still exists. May be i miss some parameters or the order of my requests has something wrong. I am trying debugpy to see if it meets my needs.

@kaisalmen
Copy link
Collaborator

Try printing the paths on both sides. I overlooked the subtle differences when I came across the problem. Are you on Linux, Windows or Mac?

@EricCD-S
Copy link
Author

EricCD-S commented Apr 8, 2025

it turns out the path format makes this problem. i tried different format, finally one works! thanks for pointing that out.

@EricCD-S EricCD-S closed this as completed Apr 8, 2025
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

2 participants