Re: [uml-user] debugging

2008-03-10 Thread Jeff Dike
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

Re: [uml-user] debugging

2008-03-10 Thread rajesh R
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 >

Re: [uml-user] debugging

2008-03-07 Thread Jeff Dike
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 > Attaching to program: /mnt/space/umlkernel/linux, process 1 F

Re: [uml-user] debugging application inside UML Kernel

2007-05-01 Thread Antoine Martin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Pranjal Kumar Dutta wrote: > Hi, > I need to debug an application running inside a UML kernel. Now > to do gdb to the running process in side UML. My application has its own > shell (CLI) and I need to debug events caused by the CLI. Can't yo

Re: [uml-user] Debugging Modules in SKAS Mode

2006-08-05 Thread Blaisorblade
On Friday 04 August 2006 02:03, Rick Spillane wrote: > How do I debug modules with the new UML? I searched around the old > website, and the link pointing to the handy-sounding script that does > it for you is broken > (http://user-mode-linux.sourceforge.net/dl-sf#UML%20utilities), this > link came

Re: [uml-user] Debugging kernel: break on every instruction?

2005-05-02 Thread Blaisorblade
On Monday 02 May 2005 10:59, [EMAIL PROTECTED] wrote: > I tried to use gdb on the kernel to analyze the TCP/IP stack. After the > first breakpoint I get a non-ending series of SIGTRAPs (I'm not sure > whether it's for every instruction or every line of code), which makes > debugging impossible. The