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

[Xen-devel] gdbserver-xen / gdb crashing domU

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] gdbserver-xen / gdb crashing domU
From: "Jonathan M. McCune" <jonmccune@xxxxxxx>
Date: Tue, 27 Sep 2005 18:49:06 -0400
Cc: bparno@xxxxxxxxxxx, Arvind Seshadri <arvinds@xxxxxxxxxx>
Delivery-date: Tue, 27 Sep 2005 22:46:44 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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
User-agent: Debian Thunderbird 1.0.2 (X11/20050602)
Hello,

I'm trying to use gdb and gdbserver-xen to walk through the instructions executed when starting up a domU kernel. We are using the current xen-unstable (linux-2.6.12-xenU). I have followed the instructions in tools/debugger/gdb/ and I am able to successfully attach to a running domU kernel. I have compiled the domU kernel with debug options as described in tools/debugger/gdb/README. After attaching to the running domU kernel, I observe the following behavior:

Issuing the gdb commands 'step', 'stepi', 'next', and 'nexti' when the domU kernel is initially paused all crash the domU kernel silently (i.e., the state of said domU goes to 'c' if you issue an `xm list` in dom0). 'continue' causes the domU kernel to boot up correctly.

All the breakpoints I've tried setting so far (setting the breakpoints before issuing the 'continue' in gdb) cause the domU kernel to panic when the function at which the breakpoint is set gets run. Functions I've tried setting breakpoints for include dup_task_struct, queue_work, scheduler_tick, and activate_task.

Is it possible to step through the domU kernel code as it is booted in Xen?

Thanks,
-Jon

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

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