On Tue, 28 Jul 2020 at 17:11, Alex Bennée wrote:
>
>
> Peter Maydell writes:
>
> > On Tue, 28 Jul 2020 at 15:10, Alex Bennée wrote:
> >>
> >> Otherwise we have an unfortunate interaction with -count sleep=off
> >> which means we fast forward time when we don't need to. The easiest
> >> way to tr
Peter Maydell writes:
> On Tue, 28 Jul 2020 at 15:10, Alex Bennée wrote:
>>
>> Otherwise we have an unfortunate interaction with -count sleep=off
>> which means we fast forward time when we don't need to. The easiest
>> way to trigger it was to attach to the gdbstub and place a break point
>>
On Tue, 28 Jul 2020 at 15:10, Alex Bennée wrote:
>
> Otherwise we have an unfortunate interaction with -count sleep=off
> which means we fast forward time when we don't need to. The easiest
> way to trigger it was to attach to the gdbstub and place a break point
> at the timers IRQ routine. Once t
Otherwise we have an unfortunate interaction with -count sleep=off
which means we fast forward time when we don't need to. The easiest
way to trigger it was to attach to the gdbstub and place a break point
at the timers IRQ routine. Once the timer fired setting the next event
at INT_MAX then qemu_s