On Wed, Nov 16, 2005 at 12:52:33PM +0800, mud dog wrote:
> This seems UML use virtual timer to simulate the Hardware Timer Interrupt?
Yup, and also SIGALRM, as you noticed.
Jeff
---
This SF.Net email is sponsore
2005/11/16, Jeff Dike <[EMAIL PROTECTED]>:
> On Tue, Nov 15, 2005 at 11:24:03PM +0800, mud dog wrote:
> > I use UML to do kernel module debug.
> > When gdb break at a breakpoint in a module function. I do next:
> > (gdb)n
> > It's not going as expected. It break at alarm_handler at
> > trap_user.c:
2005/11/16, Jeff Dike <[EMAIL PROTECTED]>:
> On Tue, Nov 15, 2005 at 11:24:03PM +0800, mud dog wrote:
> > I use UML to do kernel module debug.
> > When gdb break at a breakpoint in a module function. I do next:
> > (gdb)n
> > It's not going as expected. It break at alarm_handler at
> > trap_user.c:
On Tue, Nov 15, 2005 at 11:24:03PM +0800, mud dog wrote:
> I use UML to do kernel module debug.
> When gdb break at a breakpoint in a module function. I do next:
> (gdb)n
> It's not going as expected. It break at alarm_handler at
> trap_user.c:115 immediatly,
handle SIGVTALRM pass nostop noprint
I use UML to do kernel module debug.
When gdb break at a breakpoint in a module function. I do next:
(gdb)n
It's not going as expected. It break at alarm_handler at
trap_user.c:115 immediatly,
instead of going to the next line of current breakpoint.
What's the problem?
---
