Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
V
vscode-zil-language
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 24
    • Issues 24
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Jira
    • Jira
  • Merge Requests 0
    • Merge Requests 0
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • zilf
  • vscode-zil-language
  • Issues
  • #22

Closed
Open
Created Jul 11, 2019 by Jesse McGrew@jmcgrewOwner

[VZP-22] Memory inspector for debugging

When a variable contains an address, we should be able to show some interpretation of it, not just the number.

  • Packed string address (show the string)
  • Vocab word address (show the word and extra data)
  • Packed routine address (show the routine name)
  • Table address or internal pointer (show the table name and offset)
  • Property data address (show the object and property)

For table pointers, we should also have a way to inspect the contents of the table, ideally informed by the table format:

  • Byte table
  • Word table
  • LEXV table
  • Custom pattern defined with TABLE
  • Custom pattern defined with DEFSTRUCT

Issue metadata

  • Issue type: New Feature
  • Priority: Medium
Edited Sep 14, 2020 by Jesse McGrew
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None