WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Debugging the hypervisor

To: Matthew Donovan <matthew@xxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Debugging the hypervisor
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 21 May 2008 16:44:52 +0100
Delivery-date: Wed, 21 May 2008 08:45:33 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <60D45469A1AAD311A04C009027B6BF6806461020@SERVER20>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Aci7WZvG2o93CCdMEd2nzwAX8io7RQ==
Thread-topic: [Xen-devel] Debugging the hypervisor
User-agent: Microsoft-Entourage/11.4.0.080122
I'm rather confused about what you're trying to achieve. A good first step
would be to get Xen console output over the serial line. You achieve this by
specifying com1=115200 (for example) and console=com1,vga on Xen's command
line. If you can get that working then you can move onto the gdbstub. This
requires:
 1. that you add e.g. 'com1=115200 gdb=com1' to Xen's command line
 2. you connect to the gdbstub with gdb, not with minicom!
 3. Xen must crash for the gdbstub to be entered. The stub provides only
post-mortem debugging analysis support

 -- Keir

On 21/5/08 16:10, "Matthew Donovan" <matthew@xxxxxxxxxxxxxx> wrote:

> I am trying to debug the Xen hypervisor from a second computer over the
> serial port, but nothing seems to work.  Using mercurial, I got
> xen-3.2-testing.hg.  I followed the steps in crashdb.txt in the docs/misc/
> folder:
> set debug=y in Config.mk, crash_debug=y in xen/Rules.mk
> 
> I also added -fno-omit-frame-pointer to these file as well.
> 
> I compiled with no errors and booted with minicom connected to the
> workstation via com1 but when I do Ctrl-A three times to connect, nothing
> happens.  The debuggee boots find and gives me the login screen as normal.
> Is there a special time to hit the Ctrl-A in minicom?  Should the kernel
> wait for a connection from gdb?
> 
> I've tried various combinations of using nsplitd and a serial-split patch I
> found mentioned on mailing lists and setting the boot flags to com=1H and
> com=1.  Nothing seems to work.
> 
> Is the gdb stub working with this version of the code?
> 
> I have checked the serial connection by connecting minicom to the port and
> from the remote machine doing the command "echo test > /dev/ttyS0" and I
> receive the text.  I have minicom set for 9600 8n1 and I use the same boot
> flags set in the grub config file.
> 
> What am I missing?
> 
> Thanks
> -matthew
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>