561 karma · joined April 30, 2015
1. Weird encryption which seems to be XORing the plaintext against the same encrypted IV?
2. Using random padding instead of PKCS5 or similar?
3. Using memcmp instead of CRYPTO_memcmp or similar?
The biggest pain point was figuring out what was executing. As I mentioned, I would be playing around in the compiler, hit compile and save, and then attempt to run it in the debugger. The 'run' command either seemed to have no effect, or would run a previously compiled program, not the one I'd just written. Even typing 'reset' didn't help.
The memory didn't seem to be updating in real time either, which made things even more confusing!
Running in Firefox if that makes a difference.
- When the PC jumps, the highlighted instruction doesn't follow, leaving you lost when stepping through a program
- Can't hit enter on a blank line to repeat previous command
- No 'finish' debugger command?
- Seem to end up in random functions when stepping over simple instructions
- Am I supposed to type 'flash' or 'run' to execute my compiled program? Sometimes the one I just compiled gets executed, sometimes the one I compiled previously - how can we view what's being executed?
I really enjoyed microcorruption, and thought that UI was fine, but this feels like a step backwards.