Module browser & macro-debugger/analysis/show-dependencies fail in DrRacket only
Nobody has claimed this yet.
- Dominant language
- Racket
- Stars
- 516
- Forks
- 103
- PR merge metrics
- No merged PRs in 30d
Description
This program (an example from the docs) works with command-line racket, but fails in DrRacket:
#lang racket
(require macro-debugger/analysis/show-dependencies)
(get-dependencies 'openssl #:exclude '(racket))
The error message is:
expand: namespace mismatch; cannot locate module instance
module: #<module-path-index:"errortrace-key.rkt" errortrace/errortrace-lib>
use phase: 0
definition phase: 0
for identifier: #<syntax:/Applications/Racket v7.2/share/pkgs/errortrace-lib/errortrace/errortrace-lib.rkt:256:58 errortrace-key>
I get the same error message in a dialog when attempting View > Show Module Browser on any program I've tried it with so far, including the program above. The command-line raco show-dependencies seems to work fine.
I can get this program to run in DrRacket and View > Show Module Browser to work if, in the expanded Choose Language… dialog, I select the No debugging or profiling radio button under Dynamic Properties. I think that confirms that the error is related to errortrace (as the message suggested), though I don't really know if the fault lies with the way DrRacket uses errortrace or with errortrace itself.
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 with the Racket example in the issue and reproduce it in DrRacket with the default debugging or profiling setting. Compare the failing Module Browser and macro-debugger/analysis/show-dependencies behavior with command-line racket and raco show-dependencies; done means both DrRacket operations work without selecting “No debugging or profiling.”
Written by the indexing model from the issue text.
Assessment
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100