Closed jabdownsmash closed 8 years ago
Ah, I see why that was there now, it's causing the tests to fail.
Should be fixed.
How is this crashing p3?
It does change the interface by making next
sometimes (most of the time) return None
, but I think it should still work if you handle that...
Oh, I hadn't realized that's what was going on. I thought MemoryWatcher
was just stopping completely and python was telling me that MemoryWatcher
was None.
Handling None
looks like this though, not ideal:
for returnValue in mw:
if returnValue is not None:
address, value = returnValue
sm.handle(address,value)
It's definitely not beautiful, but I'm not a fan of blocking forever when emulation stops :P
Alright, that's that then. :)
Even when running p3 while emulation is active, this timeout procs immediately.
It's pretty nice to be able to start p3 related scripts before starting emulation anyway to ensure you get all of the addresses.