All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arun Sharma <arun.sharma@intel.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: xend crashes
Date: Fri, 19 Aug 2005 14:49:27 -0700	[thread overview]
Message-ID: <430653E7.1050308@intel.com> (raw)


I started noticing xend crashes after a misconfiguration of xmdefconfig 
around the time the xenstore changes went in. There seems to be some 
native code which doesn't seem to check for null pointers.

Traceback (most recent call last):
   File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 564, in construct
     self.configure()
   File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 965, in configure
     self.create_devices()
   File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 794, in 
create_devices
     self.create_configured_devices()
   File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 783, in 
create_configu
red_devices
     self.createDevice(ctrl_type, dev_config)
   File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 392, in 
createDevice
     backdb = backdom.db.addChild("/backend/%s/%s/%d" %
TypeError: int argument required
<xend crash>

The crash seems to happen after releaseDomain.

[2005-08-19 16:23:35 xend] WARNING (XendDomainInfo:993) Unknown config 
field vnc
[2005-08-19 16:23:35 xend] DEBUG (blkif:24) exception looking up device 
number f
or ioemu:hda: [Errno 2] No such file or directory: '/dev/ioemu:hda'
[2005-08-19 16:23:35 xend] INFO (xsobj:337) DBMap>releaseDomain> 1

gdb doesn't seem to be helpful.

0xfbffd402 in ?? ()
(gdb) c
Continuing.
[New Thread -1255515216 (LWP 4824)]
(XEN) audit1
(XEN) audit1 done
(XEN) audit2
(XEN) audit2 done
(XEN) audit3
(XEN) audit3 done
Couldn't get registers: No such process.
(gdb) x /i $eip
Cannot fetch general-purpose registers for thread -1247122512: generic error

	-Arun

                 reply	other threads:[~2005-08-19 21:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=430653E7.1050308@intel.com \
    --to=arun.sharma@intel.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.