Re: RDI code busy-waiting on running target?

Keith Seitz
2002-07-11T23:53:42Z

On Thu, 11 Jul 2002, Grant Edwards wrote:

> Here's a patch that fixes it. I only added the usleep() when
> there's no ui_loop_hook to call. Is that the right thing to
> do, or will Insight et al still suck CPU time? I'm not sure
> who's supposed to be surrendering the CPU, the UI or the
> target.

Insight would definitely shoot to 100% CPU, too. This often a problem with
have gdb non-event based w.r.t. the target. I would recommend doing the
sleep for the ui_loop_hook, too.

Keith