[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] Debugging DomU
- To: Purav Saraiya <purav@xxxxxxxxxxxxx>
- From: Kip Macy <kip.macy@xxxxxxxxx>
- Date: Sun, 4 Dec 2005 21:50:19 -0600
- Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
- Delivery-date: Mon, 05 Dec 2005 03:50:05 +0000
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=CsEuuTaJ296Xvg8fQ2UcPIxWzvuVMmWlwEArQQu3CkgpO9h1PSLIUk2eSOfysakY1/LsGCnRA7fJIpEC1jnpZuiOtbsWEKRbYFg4mj00SN8KKKBDoSsOPoYrkVfIjlJJl8fd1rOfQ/54JDopbAaUNYS2xWiavCuC/NnrHKMY3qc=
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
With the patches I've sent today domu_debug is now a run-time option.
Enabling crash_debug will not interfere with domU debugging.
-Kip
On 12/1/05, Kip Macy <kip.macy@xxxxxxxxx> wrote:
domu_debug and crash_debug are mutually exclusive.
On 11/19/05, Purav Saraiya <
purav@xxxxxxxxxxxxx> wrote:
I am facing problems with debugging DomU.
I have made changes in the gdt table in the file
head.S for Dom U. Because
of that the domain is crashing.
For debugging, I followed the steps mentioned in the file
/xen-unstable/tools/debugger/gdb/README. I also made changes in the
/xen/Rules.mk file and compiled domU with -g C flag.
However, as mentioned in the README file no
/var/xen/dump/<Domain-name>.<DomainID>.core file is generated.
Rules.mk file :
verbose ?= y
debug ?= y
perfc ?= n
perfc_arrays?= n
domu_debug ?= y
crash_debug ?= y
Am I missing something?
Thanks for replies.
-Purav
_______________________________________________
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
|
