you are viewing a single comment's thread
view the rest of the comments
[–] 6 points 1 year ago (3 children)

🤔 that reminds me of the brainfuck debugger I wrote. Good fun

  • source
  • hideshow 3 child comments
  • [–] [S] 5 points 1 year ago (2 children)

    cool! i once tried to write a brainfuck jit compiler (that just appends raw bytes to a buffer and runs it as x86 machine code if it hits a branching instruction like [ / ])

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 1 year ago (1 child)

    That's cool. Mine is just an interpreter for execution but it has breakpoints, watchpoints, and save states. I've thought about trying to do some form of JIT or at least AOT but I haven't yet made an attempt. Besides for a debugger that's counter productive.

  • source
  • parent
  • hideshow 1 child comment
  • [–] [S] 3 points 1 year ago

    save states are something i've seen very few debugger-enabled interpreters have. on paper, it would probably be as easy as storing the state of the interpreter in a format like a core dump (only requires the ability of reflection)

  • source
  • parent