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

Memory view #60

Open
BacchusFLT opened this issue Oct 16, 2020 · 2 comments
Open

Memory view #60

BacchusFLT opened this issue Oct 16, 2020 · 2 comments

Comments

@BacchusFLT
Copy link

I guess this is your own tool:

https://kickassmemoryview.insoft.se/

A thought would be if that function was made native on the supported platforms and could be enabled in the build to visualise the memory usage... (it's presumably exponentially difficult if it would also support a project or even a single source with multiple files with binary imports and patches, but that would also be part of the wishlist from me; visualising import of file xyz.prg between 0800 to cfff, with patches on locations x,y and z in addition to the plain list of what the pure source file generated as output from its assembly of opcodes).

@Swoffa
Copy link
Owner

Swoffa commented Oct 25, 2020

Thanks @BacchusFLT!
Exactly this has been in my mind for quite some time, but I did not get the chance to try it out and fix it...yet. Hopefully I will, especially now when I know that someone else would also benefit from it.

@BacchusFLT
Copy link
Author

BacchusFLT commented Oct 25, 2020

My cracks are likely amongst the most complex use cases. Loading files, patching then and saving them back. I'd be happy to test.

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

No branches or pull requests

2 participants