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] gdbserver-xen / gdb crashing domU

To: "Jonathan M. McCune" <jonmccune@xxxxxxx>
Subject: Re: [Xen-devel] gdbserver-xen / gdb crashing domU
From: Kip Macy <kip.macy@xxxxxxxxx>
Date: Wed, 28 Sep 2005 11:48:00 -0700
Cc: bparno@xxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, Arvind Seshadri <arvinds@xxxxxxxxxx>
Delivery-date: Wed, 28 Sep 2005 18:45:39 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=fmWj//oUWOyzMgslJZ85+tc1VmrDuQqhJ5YM10Qo6SHFR2dX0RCUE7pnOLAxvir6kyViQoWiCrGxWo5gssbLyYZqCNxYuEHRvuF1ha/3Mc5j55WvTOBWKXlCMbbRiLGMeDt38Gw3OUP63VM8V6ycYzfhd+jG6WC1mfm0zeX1Y6U=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <433AA977.8010506@xxxxxxx>
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>
References: <4339CC62.4040102@xxxxxxx> <b1fa2917050927185970a3c2b5@xxxxxxxxxxxxxx> <433AA977.8010506@xxxxxxx>
Reply-to: Kip Macy <kip.macy@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I vaguely recall it depending on debug as silly as that sounds. I'll have to go back and take a look - xen clearly isn't pausing the domain when an int3 is hit.
 
      -Kip

 
On 9/28/05, Jonathan M. McCune <jonmccune@xxxxxxx> wrote:
Hi Kip,

Thanks for your quick response.  Unfortunately, in the experiment I
described in my first post, I did have domu_debug=y in xen/Rules.mk.  I
rebuilt and reinstalled xen after a `make clean` in the xen subdir just
to be sure it would have picked up the change.

Any other ideas?

Thanks,
-Jon

Kip Macy wrote:

>domu_debug must be enabled in xen's Rules.mk <http://Rules.mk>, otherwise
>the int3 gets passed onto the OS which will cause it to crash as it isn't
>expecting to see a debug trap in ring 0 (unless of course you have a
>debugger compiled into the kernel itself).
>
>Just re-compile and then pass -p (pause) to xm create followed by an attach
>with gdbserver-xen.
>
>-Kip
>
>On 9/27/05, Jonathan M. McCune < jonmccune@xxxxxxx> wrote:
>
>
>>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
>>
>>
>>
>>_______________________________________________
>>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