PSX debugger can't evaluate multiple breakpoint conditions (2.6.2)

Summary

PSX debugger only evaluates breakpoint hits using the first break condition. When adding multiple read/write conditions for different addresses, the emulator ignores every condition except the first despite read/writes happening to these other addresses. Deactivating or deleting the first condition don't make any other condition work, you have to delete all conditions and then add the next condition as the first in order for the debugger to detect a breakpoint hit.

Repro

1. Add multiple breakpoint conditions that you're sure you're going to hit in the next frame. Only the first condition will hit.
2. To make sure that other conditions aren't being evaluated, you can toggle the first condition off and check whether the address of the other condition are being changed. Despite the changes happening, the emulator doesn't detect breakpoint hits.

Host env.

• BizHawk 2.6.2; Windows 10 Home, AMD processor.

Start by reproducing the issue in the PSX debugger on BizHawk 2.6.2 using multiple read/write breakpoint conditions, then trace the debugger's breakpoint-condition evaluation path. Done means each active condition can trigger independently, including conditions added after the first, while toggling or deleting one condition does not disable the others.