Bug 324799

Description Chris McCormick 2010-09-08 16:52:32 EDT

If you open RTA on an already halted target, RTA does not receive the ‘onHalted’ event, so it doesn’t gather the stop mode data. Manually hitting the refresh button doesn’t work, either, since stop mode doesn’t do the read until it receives both an ‘onHalt’ event and a ‘refresh’ request (or auto-refresh is on). This is to prevent the data being read multiple times on a halt and to prevent the data from being read while the target is running. 

The simple fix for this would be to have RTA fake an onHalted event when it’s launched if the target is currently halted.

However, this exposes another problem we have. If you start at cint00 and open RTA, if stop mode tries to read the records it may send up old records which break Bruce’s end. I think this makes RTA unusable for anyone starting at cint00.

So we may need to fix the second issue before we can fix the first one. Or, it may be possible to get the ‘refresh’ button working so that the user can manually force the refresh, though this seems less ideal from a user perspective.

UIA will have this same problem, we haven’t done anything there yet that I know of to address it.  

Another approach would be for the host to be more tolerant of out of order data.

I thought there may be CQs filed for these issues, but I couldn't find any.