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

Create option for a log containing hit breakpoints and/or [selected] memory value changes in Load mode #69

Open
reeelix opened this issue May 5, 2024 · 2 comments
Labels
accepted This issue/feature is accepted and will be worked on enhancement New feature or request

Comments

@reeelix
Copy link
Collaborator

reeelix commented May 5, 2024

In Load mode, a hotkey of some sort enables a log in a seperate pane.

This log contains one or both of the following (i am not sure yet):

  • For each Breakpoint that has been hit, an entry in the form of BP in line 9 hit
  • For each value change in memory, an entry in the form of [h1]: 436 -> 437

For the second point, there might be the option to not include changes on all memory cells/accumulators/..., but only on some (that can be selected in some way). This selection would have to include a way to select index memory cells that are not yet contained in the memory cell listing on the right side.

@reeelix reeelix added the enhancement New feature or request label May 5, 2024
@reeelix
Copy link
Collaborator Author

reeelix commented May 5, 2024

this shouldn't be priority

@LMH01
Copy link
Owner

LMH01 commented May 5, 2024

I like this idea, implementing it should not be too complicated (that is if we don't make memory values selectable and instead output everything that changes to the pane). I don't think that outputting everything in the log will be a bad idea, as there is at max one value that is changed per instruction (however this looks different, when run to breakpoints is used, but I think that is for now something we would have to life with).

@LMH01 LMH01 added the accepted This issue/feature is accepted and will be worked on label May 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted This issue/feature is accepted and will be worked on enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants