All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Rousse <Guillaume.Rousse@inria.fr>
To: xen-devel@lists.xensource.com
Subject: Re: xend crash for freeing invalid pointer in python
Date: Tue, 13 Nov 2007 22:46:49 +0100	[thread overview]
Message-ID: <473A1B49.20304@inria.fr> (raw)
In-Reply-To: <473A1984.6010406@inria.fr>

Guillaume Rousse a écrit :
> Hello.
> 
> I'm the mandriva xen package maintainer. I'm trying to figure out a
> strange crash occuring on mandriva 2008.0 (latest stable version): xm
> list (actually, any xm use) crashes with the attached stacktrace in the
> logs. I installed the debug symbols for python and xend, but I don't
> know how to invoke gdb on a python script for getting the stacktrace myself.
> 
> Strangelly, everything is fine on 64 bits version :/
> 
> All binaries are built with the following flags:
> -O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector
> --param=ssp-buffer-size=4 -fexceptions -fomit-frame-pointer -march=i586
> -mtune=generic -fasynchronous-unwind-table fno-strict-aliasing
> 
> The spec file is rewievable from
> http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/xen/current/SPECS/
> 
> The patches are availabe from
> http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/xen/current/SOURCES
Sorry, this is for the cooker (development version) package.

The one causing troubles on stable version is at
http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/branches/2008.0/xen/releases/3.1.0/2mdv2008.0/

-- 
Guillaume Rousse
Moyens Informatiques - INRIA Futurs
Tel: 01 69 35 69 62

  reply	other threads:[~2007-11-13 21:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13 21:39 xend crash for freeing invalid pointer in python Guillaume Rousse
2007-11-13 21:46 ` Guillaume Rousse [this message]
2007-11-15 12:11 ` Guillaume Rousse

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=473A1B49.20304@inria.fr \
    --to=guillaume.rousse@inria.fr \
    --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.