[Feature Request] Register breakpoints, conditional breakpoints, and control flow tracing

[dio-gh]

• Would be pretty nice if you could put breakpoints on registers (read/write/read+write/access), so that you could just ignore whatever else that's being executed, and be able to follow the journey of a given variable and it's mutations only, instead.
• This would be very nicely complemented by some sort of control flow tracing feature, such that between two bp hits, every kind of change in the control flow (any one of the branching instrs or the ctr-related jumps being executed) on the given thread would be printed to the logs.
• Finally, being able to set conditional breakpoints would also be useful sometimes. Especially so, if [Feature Request] debugger: Memory breakpoints #9621 becomes implemented. A couple examples:
• conditional instr bps:
  to be able to craft a bp that e.g. breaks on any load instr, if *(ra+d) equal to something. or to break if its some specific instruction, but only with certain register values.
• conditional register bps:
  to be able to craft a bp that e.g. breaks when a register is a given value - useful if a given function is generic, and will iterate through multiple objects in memory, but you are only curious about a certain one.

[elad335]

About register breakpoints, what if RPCS3 could give you the exact address of memory represnting the emulated register then use CE?

[dio-gh]

It would be an okay workaround. I wouldn't tick the appropriate checkbox for it though. Like I'm guessing its just at an offset, like cia is at +0x474.