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

Debugger Woes Tracking Issue #36

Open
2 of 6 tasks
iwillspeak opened this issue Oct 12, 2021 · 1 comment
Open
2 of 6 tasks

Debugger Woes Tracking Issue #36

iwillspeak opened this issue Oct 12, 2021 · 1 comment
Labels
feature New feature or request Roadmap Larger scale planned feature or tracking issue

Comments

@iwillspeak
Copy link
Owner

iwillspeak commented Oct 12, 2021

Our current debugger support is a bit rough around the edges.

  • Bound tree contains sequence points for debuging
  • Debuggable REPL. Embedded source in PDBs?
  • Stop at entry, and step in.
  • Inferred (nop based) sequence points for debug builds. (DisableSymbolStoreSequencePoints)
  • No symbol information for local names, or environment slots.
  • Better lambda names. e.g. foo_1::bar_0 not lambda1::lambda0 if (define (foo ..)) forms are used.
@iwillspeak iwillspeak added feature New feature or request Roadmap Larger scale planned feature or tracking issue labels Oct 12, 2021
@iwillspeak
Copy link
Owner Author

symbol names could be attached to storage when a new storage is alloccated by the binder context, or we could keep a mapping from storage to name hint. When emitting debug information later we could just inspect this mapping.

The latter would provide two advantages:

  • we don't have to store the name with the storage each time it is referenced
  • We can re-write the storage -> name mapping more easily in lower.
  • We can store name information for storage other than locals here too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request Roadmap Larger scale planned feature or tracking issue
Projects
None yet
Development

No branches or pull requests

1 participant