On Mon, May 11, 2009 at 12:17:23PM +0100, Daniel P. Berrange wrote:
> Several methods forgot to call virEventInterruptLocked() in critical
> times, or called it at the wrong point. This fixes that problem.
>
> It also changes watch and timer numbers to start from 1, instead of 0.
> This is because
Several methods forgot to call virEventInterruptLocked() in critical
times, or called it at the wrong point. This fixes that problem.
It also changes watch and timer numbers to start from 1, instead of 0.
This is because we've had a number of bugs where code has passed an
uninitialized timer/watch
