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

Visible memory inspector #1318

Open
MobyGamer opened this issue Nov 5, 2019 · 0 comments
Open

Visible memory inspector #1318

MobyGamer opened this issue Nov 5, 2019 · 0 comments

Comments

@MobyGamer
Copy link

During reverse-engineering or debugging programs, it would be educational to have a visible memory inspector feature of the debugger. An area of memory could be indicated by either segment:offset in real mode, or absolute address in protected mode. The area could be visualized in a rectangular window, the dimensions and color depth (ie. how many bits per pixel) could be specified by the user. This window would remain open until closed, and would live-updated as the program runs or is stepped through in the debugger.

The intended use of this feature is to see back buffers of graphics screens before they are made visible. For example, games that run in CGA sometimes write to a linear 16K buffer before they are REP MOVSW'd to the visible interlaced buffer, performing translation in the process. Having the back buffer visible would allow inspection of how the game engine operates when limited by CGA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants