On 3/7/08, Jeff Dike <[EMAIL PROTECTED]> wrote:
>
> On Fri, Mar 07, 2008 at 05:56:48PM +0530, rajesh R wrote:
> > (gdb) set args debug=parent gdb-pid=19137
> > (gdb) show args
> > Argument list to give program being debugged when it is started is
> > "debug=parent gdb-pid=19137".
> > (gdb) att 1
>
>
> The first thing to do is make sure you have a way of virtualizing
> Linux (int 0x80/sysenter/syscall) system calls, which means that you
> can prevent them from executing on the host, you can read the system
> call and the arguments, and make it return with the result of your
> choice, inc
On Mon, Mar 10, 2008 at 05:46:05PM +0530, rajesh R wrote:
> > Follow these instructions instead -
> >http://user-mode-linux.sourceforge.net/hacking.html
> >
> > Now, it's no different from debugging anything else.
> >
> >Jeff
> >
> >
> > --
> > Work email - jdike at
On Mon, Mar 10, 2008 at 07:30:04PM +0530, Pravin wrote:
> >
> > You also need to be able to intercept and nullify signals.
>
> I am not very clear about this, But how does UML deals with interrupts
> or how they r simulated ?
ptrace allows child signals to be intercepted and nullified. Signals
>
> ptrace allows child signals to be intercepted and nullified. Signals
> from the host are the equivalent of hardware interrupts. The UML
> kernel makes its own decisions about signals to its own processes, and
> those are delivered in the same way as any other architecture.
>
>
> > Is the
