Re: [Qemu-devel] Make QEMU more friendly for kernel debug

2006-02-26 Thread prime
On 2/26/06, Tace <[EMAIL PROTECTED]> wrote: Hi,Please do...I got a question, doesn't disable the interrupts changes theunderlying system? Perhaps a good way would be to monitor thecompletion of the interrupt routine before singlestepping to the next instruction?On 2/23/06, prime <[EMAIL PRO

Re: [Qemu-devel] Make QEMU more friendly for kernel debug

2006-02-25 Thread prime
On 2/25/06, Mulyadi Santosa <[EMAIL PROTECTED]> wrote: Hi..> So I modify> QEMU's source code to disable interrupts in single step mode,and now> I can use "step" or "next" command in gdb to single step>  functions. very interesting! Please post your patch on qemu-devel and preferably onqemu.dad-answ

Re: [Qemu-devel] Make QEMU more friendly for kernel debug

2006-02-25 Thread Mulyadi Santosa
Hi.. > So I modify > QEMU's source code to disable interrupts in single step mode,and now > I can use "step" or "next" command in gdb to single step > functions. very interesting! Please post your patch on qemu-devel and preferably on qemu.dad-answers.com too. Personally, I'd be glad to review

[Qemu-devel] Make QEMU more friendly for kernel debug

2006-02-25 Thread prime
Hello everyone,    I find that I can't single step OS kernels use qemu.When I use "step" or "next" command in gdb,the kernel always enter its interrupt route instead of executing the next instruction after the breakpoint.So I modify QEMU's source code to disable interrupts in single step mode,and

[Qemu-devel] Make QEMU more friendly for kernel debug

2006-02-24 Thread prime
Hello everyone,    I find that I can't single step OS kernels use qemu.When I use "step" or "next" command in gdb, the kernel always enter its interrupt route instead  of executing the next instruction after the breakpoint.So I modify QEMU's source code to disable interrupts in single step mode,an