Issues using dolphin's debugger

[Fullmetal5]

Currently I'm experiencing some weird behavior with dolphin's debugger. At this point I just wanna know if I'm doing something wrong or if the debugger is just buggy.

First I should say I've experienced some inaccuracies with the JIT Recompiler (exceptions triggered on instructions that can't possibly cause that type of exception (ex. an MR instruction causing an "invalid read from address" exception)) so I currently have it on the Interpreter for better accuracy.

The first example is something that has gotten annoying and I do think is an actual bug.
Without setting any breakpoints and triggering the bug in the Internet Channel a couple of exceptions are generated as expected and the game hangs however dolphin still functions just fine.
However, when setting a breakpoint and then triggering the bug the breakpoint is hit as expected but when I step then play to keep the game running dolphin simply hangs (not crashes just hangs) and I am forced to quit it from the terminal.

Is this just me miss using the debugger or is this a bug?

I realize I am being vague with what the actual bug is but I wrote it like because to trigger the bug requires me setting up some server somewhere so that people can reproduce the behavior and all I am trying to do is see if I'm using the debugger incorrectly.

Realized after posting that this should go under the Support area and not the Development area. If that is where it should be then can a mod move it over there?

My Specs:
OS: Arch Linux x86-64
Graphics: Intel Integrated Graphics
RAM: 8GB
CPU: Intel® Core™ i7-4790K CPU @ 4.00GHz
Dolphin-version: latest git (as of typing this) (4d0dd930981daa0638e3ed62dcb9ae5678af3fce)

[skid]

To maintain performance, exceptions do not get triggered straight away. This is the reason why you are seeing exceptions occurring on unexpected instructions - the exception was triggered by an instruction in the near past. According to the PPC manual this is acceptable, but I think Dolphin triggers the exception much later than the real hardware.

The Interpreter was triggering the exception at the instruction that caused it, but I think this was changed to match the JIT so that the Dolphin developers could make comparison runs between the JIT and Interpreter to debug issues with the CPU emulation.

[Fullmetal5]

Thank you, that would indeed explain some of the weird stuff I have been seeing and just assuming that I doing something wrong.

Unfortunately that makes things very difficult to work with. I don't take it there is anyway to force it to do something like a "break on exception"?

[skid]

There isn't an option for it in Dolphin so you'd have to modify the Dolphin source code.