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

Re: [Xen-devel] trying to debug xen4 & qemu-dm, Xen reports "core dump failed"


  • To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • From: 0bo0 <0.bugs.only.0@xxxxxxxxx>
  • Date: Tue, 26 Jan 2010 14:47:38 -0800
  • Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Tue, 26 Jan 2010 14:47:55 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=UyoICe/OoIeSY3MZV1mOOmJeaVpyukNI5wDV754vc6J3q5ZMXS1l3rnu3++Avw8i+4 Mbo5ZzRKYOJmpqWlYc4cSbcPrfG1dbnYxcNjacpNXi7Qux+IMupogS7QFa5A7iIFiidM 7jHo/X5YhyomRox3IV+wl+juPKAXcN3HxZaHA=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On Tue, Jan 26, 2010 at 2:30 PM, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> wrote:
>>> Now try starting your guest. It fails, and hopefully you have a core file in
>>> /var/core/. You can load it into gdb as 'gdb /usr/lib/xen/qemu-dm
>>> /var/core/name-of-core-file' and then execute bt command at the gdb prompt.
>>> That hopefully tells us where qemu-dm crashed.
>>
>> bash
>> ulimit -c unlimited
>
> Actually that probably only enable core dumps for the shell you are running.
> Qemu-dm will inherit its ulimits from xend. So you need to enable core dumps
> by running 'ulimit -c unlimited' before you start xend, or put it in the
> startup script that starts xend. You could also script the echo to
> /proc/sys/kernel/core_pattern, but it's definitely safe to do that later
> from a shall, as it's a global value, rather than per-process.

bash
ulimit -c unlimited
echo '/var/core/core.%e.%u.%p' > /proc/sys/kernel/core_pattern
mkdir -p /var/core
cat /proc/sys/kernel/core_pattern
/var/core/core.%e.%u.%p

service xend restart
xm create /etc/xen/vm/test.cfg
ls -al /var/core/ | grep core
  -rw-------  1 root root 4542464 2010-01-26 14:36 core.qemu-dm.0.7772

gdb /usr/lib64/xen/bin/qemu-dm /var/core/core.qemu-dm.0.7772
  ...
  /usr/lib64/xen/bin/qemu-dm: Too many levels of symbolic links.
  Missing separate debuginfo for the main executable file
  Try: zypper install -C
"debuginfo(build-id)=9326caa0db4accd719f10b02a9a41a40c10b662a"
  Core was generated by `/usr/lib/xen/bin/qemu-dm -d 4 -serial pty
-domain-name test -videoram 4 -k en-u'.
  Program terminated with signal 11, Segmentation fault.
  #0  0x000000000047b974 in ?? ()
  (gdb) quit

zypper install -C "debuginfo(build-id)=9326caa0db4accd719f10b02a9a41a40c10b662a"
  Loading repository data...
  Reading installed packages...
  'debuginfo(build-id)=9326caa0db4accd719f10b02a9a41a40c10b662a' not found.
  Resolving package dependencies...

so where/how do I get the debug symbols?

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


 


Rackspace

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