DrRacket Crashes on Debug Rerun on Earlier Stack-frame
Nobody has claimed this yet.
- Dominant language
- Racket
- Stars
- 516
- Forks
- 103
- PR merge metrics
- No merged PRs in 30d
Description
I’m submitting this report in case it is helpful. The workaround is to stay on the last stack-frame when rerunning. I checked every mention of crashing in existing issues, and no one appears to have reported this issue. On 2 different laptops with Windows 10, and DrRacket version 8.8, this crash is easily reproducible. For your convenience, I put the below code and the steps to reproduce in a file that you can just run.
#lang racket
;Run this in debug mode
(define (inner)
(void))
(define (outer)
(inner)) ;Put a break-point here
(outer)
;Hit Go. Click on the earlier stack-frame.
;Click on Debug again. CRASH!
Here is the crash stack-trace. Let me know if you need more information from me to be helpful to you.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the supplied code from code.zip in DrRacket 8.8 on Windows 10 in debug mode, following the earlier-stack-frame rerun steps. Read Stack-trace.txt and use the debug-mode and stack-frame path as the entry point for investigation. Done means the reproducible sequence no longer crashes.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100