Author Topic: Monogams to behave more like a file based hex editor.  (Read 468 times)

0 Members and 1 Guest are viewing this topic.

Offline m_dr_m

  • CPC6128
  • ****
  • Posts: 236
  • Country: se
    • OrgaMS!
  • Liked: 162
  • Likes Given: 173

I wish to improve Monogams (OrgamS's monitor) for hackers, programmers and fair investors.

Imagine you are searching for cheat code / easter egg / hidden message in a program.

Old fart way of doing things (Hackit/ Le Hackit):
  • Have your program in RAM
  • Search for some opcodes or markers
  • Note all the addresses (except the spurious ones)
  • Visit each address
New art cracking:
  • Let Monogams load the program in a dedicated space. So the search is restricted to the program area, hence faster and non-disturbing. Also, it wouldn't overwrite the first 128k, so we can still work with your own stuff.
  • Inline search (e.g. go to prev/next occurrence in memory-view or disassemble mode, nothing to write down), allowing wildcards and smart searches (i.e. "who jumps to this address?" even with JR).
But sometimes, that's just the raw memory you want to inspect.
That's why I want to introduce the concept of clips, which could be:
  • A file
  • A snapshot of a memory area
  • Live view of a memory area.
The last one could be used to track variables in step-by-step debugging.
Combined, 2/3 can be used to make a diff "before vs after".

Would we be interested by using that? By coding that?
Which interface would you like (e.g. syntax to define a clip?).