Deadlock in UI about rars HOT 5 CLOSED

Thanks for the report. I can reproduce this, but it may take some time to debug it.

It looks like this might be caused by updating UI elements from the RISCV thread through the observer interface. It should be fixable by making the observers schedule a UI update rather than doing it.

from rars.

This should be fixed now. Would you please confirm?

I'll still need to check other areas to see prevent any other similar problems so I'll leave this open until I check on them.

from rars.

So there indeed was a similar problem with the run button. If you set up your program with every line breakpointed and then hit run a bunch it will end up throwing a null-pointer exception.

I fixed that in 6afb286, so I'll close this once you confirm the problem is fixed for you.

from rars.

Sorry for my late response.

All my programs run while stepping fine, so it seems to be fixed.

Thanks!

from rars.

Great. Thanks for helping squash this bug.

from rars.