-
-
Notifications
You must be signed in to change notification settings - Fork 91
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
The racket-debug-run-to-here
doesn't work
#597
Comments
The space after that closing paren in If you use the nand p keys (next and previous), it will move among currently breakable positions. At any of those, you can press h to "run to here". From that you'll see that it can break on the closing paren in Does this help? Admittedly this might not be the most intuitive/discoverable UX, so, I'm definitely open to suggestions how to improve. |
Do you mean after entering debug mode (i.e. press M-x racket-run-with-debugging), then press For the example in the topic, it told me "No breakable positions in this buffer". |
Yes.
Using your example file, my steps:
|
I have followed your steps, but Emacs complained: No breakable positions in this buffer, then exited the debug mode. Racket Logger
Which Racket version do you use? Any suggestion for debugging the issue? |
At the moment I'm using Racket built from source, which is ~= Racket 8.4. Not to go off on a tangent (although maybe it matters?) I'm surprised by your
FWIW my logger output -- with
|
Another debugging idea: At step 2 of these steps, what if you:
For me it is something like:
|
OK I have a commit I believe will fix this. Although I haven't tested it yet on Windows, it definitely fixes what I think is a similar problem when using a remote back end. I plan to merge this after it passes CI. At that point, I'd be grateful if you try it on Windows and confirm it there, too. If not, please feel free to re-open this issue, and I'll dig deeper hands-on with Windows. |
I tried your patch. It has the same problem, i.e. pressing "SPACE" to step is OK, but can't do
Before your patch:
After your patch:
I also tried to set
The following is the logs in Racket Logger: Initial (it seems that the Racket Logger will open automatically as long as a ,rkt file open)
After
After
Press Place mouse cursor at Noticed that after
|
No reopen button. |
Be sure to use racket-file-name-front-to-back on the file name given to the back end by racket-debug-run-to-here. Also, although not part of the original bug report, make sure the breakable positions are sorted. Once upon a time the back end might have done this but it certainly doesn't today; do so in the front end.
I'm sorry that didn't resolve it. Thank you for all the additional details. It looks like commit 52e993f fixed "one half" of the problem for Windows --- the back end notification of the breakable positions includes a file name, which needs to be translated. But now I see there's also a problem with To address that I pushed to a topic branch commit 1bb7c89. This fixes things fully, for me, when I test it hands-on using Windows. Before I merge that, I'll wait awhile in case you're willing/able to try that and confirm it works for you, too. |
It works nicely, thanks! |
Hi, I watched the video and tried the debugging mechanism in racket-mode.
For example,
I press
M-x racket-run-with-debugging
and press "SPACE" to step. It works fine. Thank you for this great work.However,
racket-debug-run-to-here
doesn't seem to work? In the debug mode, I placed the mouse cursor at(f 41) |
and pressh
, the debugger stopped.My racket-mode version is racket-mode-20220216.1917 from elpa, operation system windows7, Racket v8.0 [bc].
Related issue: #425
racket-bug-report:
The text was updated successfully, but these errors were encountered: