[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] garbage registers when domain killed by xen

  • To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Kip Macy <kip.macy@xxxxxxxxx>
  • Date: Fri, 6 May 2005 18:26:17 -0700
  • Delivery-date: Sat, 07 May 2005 01:25:54 +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:mime-version:content-type:content-transfer-encoding:content-disposition; b=k0dJrKFJaj6hCDfAiqHDq2Wz8n78GhxKnlsV01Nm9ddd6cq6ulljBrM9oamoBexApFUwxsK2EBF952iP407cbZ9qFakg2wyfS5+sfKTdqeB1TUUJ/jiZH9CBwwe18uIISjZax7O98x9SFonsvY8kunEfl3CeT8Rc/mC0aKGge2E=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

The coredumps that I'm getting from a domain that crashes without
calling domain_crash are not terribly useful. These are the register
(gdb) i r
eax            0x6000   0x6000
ecx            0xfbc06000       0xfbc06000
edx            0xfbc06040       0xfbc06040
ebx            0x4      0x4
esp            0xc02a9008       0xc02a9008
ebp            0xc02aed78       0xc02aed78
esi            0x4      0x4
edi            0x2      0x2
eip            0x0      0x0
eflags         0x10216  0x10216
cs             0x819    0x819
ss             0x821    0x821
ds             0x821    0x821
es             0x821    0x821
fs             0x821    0x821
gs             0x821    0x821

Is it really necessary for xen to overwrite part of a domain's context
on a fatal trap?


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.