From: Christophe Fergeau <cfergeau@redhat.com>
To: Fabio Fantoni <fabio.fantoni@m2r.biz>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Anthony PERARD <anthony.perard@citrix.com>,
spice-devel@lists.freedesktop.org,
Laszlo Ersek <lersek@redhat.com>
Subject: Re: [Qemu-devel] [Spice-devel] [Xen-devel] Qemu 2.0 regression with xen: qemu crash on any domUs S.O. start
Date: Mon, 7 Apr 2014 12:20:40 +0200 [thread overview]
Message-ID: <20140407102040.GJ3724@teriyaki.redhat.com> (raw)
In-Reply-To: <534276EA.9010200@m2r.biz>
[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]
On Mon, Apr 07, 2014 at 11:59:06AM +0200, Fabio Fantoni wrote:
>
> Today I did some tests also with hvm and spice and I found another
> segfault with different backtrace to solve:
> >(gdb) c
> >Continuing.
> >
> >*Program received signal SIGSEGV, Segmentation fault.**
> >**0x0000555555855d30 in interface_client_monitors_config
> >(sin=0x5555563b0260, **
> >** mc=0x0) at ui/spice-display.c:557**
> >**557 if (mc->num_of_monitors > 0) {*
>
> >(gdb) bt full
> >#0 0x0000555555855d30 in interface_client_monitors_config (
> > sin=0x5555563b0260, mc=0x0) at ui/spice-display.c:557
> > ssd = 0x5555563b0210
> > info = {xoff = 0, yoff = 0, width = 0, height = 0}
> > rc = 32767
> > __func__ = "interface_client_monitors_config"
> >#1 0x00007ffff4af5113 in ?? ()
> > from /usr/lib/x86_64-linux-gnu/libspice-server.so.1
> >No symbol table info available.
A backtrace with spice-server debugging symbols installed would be helpful.
Christophe
[-- Attachment #2: Type: application/pgp-signature, Size: 181 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Christophe Fergeau <cfergeau@redhat.com>
To: Fabio Fantoni <fabio.fantoni@m2r.biz>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Anthony PERARD <anthony.perard@citrix.com>,
spice-devel@lists.freedesktop.org,
Laszlo Ersek <lersek@redhat.com>
Subject: Re: [Xen-devel] [Qemu-devel] Qemu 2.0 regression with xen: qemu crash on any domUs S.O. start
Date: Mon, 7 Apr 2014 12:20:40 +0200 [thread overview]
Message-ID: <20140407102040.GJ3724@teriyaki.redhat.com> (raw)
In-Reply-To: <534276EA.9010200@m2r.biz>
[-- Attachment #1.1: Type: text/plain, Size: 1013 bytes --]
On Mon, Apr 07, 2014 at 11:59:06AM +0200, Fabio Fantoni wrote:
>
> Today I did some tests also with hvm and spice and I found another
> segfault with different backtrace to solve:
> >(gdb) c
> >Continuing.
> >
> >*Program received signal SIGSEGV, Segmentation fault.**
> >**0x0000555555855d30 in interface_client_monitors_config
> >(sin=0x5555563b0260, **
> >** mc=0x0) at ui/spice-display.c:557**
> >**557 if (mc->num_of_monitors > 0) {*
>
> >(gdb) bt full
> >#0 0x0000555555855d30 in interface_client_monitors_config (
> > sin=0x5555563b0260, mc=0x0) at ui/spice-display.c:557
> > ssd = 0x5555563b0210
> > info = {xoff = 0, yoff = 0, width = 0, height = 0}
> > rc = 32767
> > __func__ = "interface_client_monitors_config"
> >#1 0x00007ffff4af5113 in ?? ()
> > from /usr/lib/x86_64-linux-gnu/libspice-server.so.1
> >No symbol table info available.
A backtrace with spice-server debugging symbols installed would be helpful.
Christophe
[-- Attachment #1.2: Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2014-04-07 10:21 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 15:01 [Qemu-devel] Qemu 2.0 regression with xen: qemu crash on any domUs S.O. start Fabio Fantoni
2014-04-01 15:01 ` Fabio Fantoni
2014-04-01 16:24 ` [Qemu-devel] " Laszlo Ersek
2014-04-01 16:24 ` Laszlo Ersek
2014-04-02 11:13 ` [Qemu-devel] " Fabio Fantoni
2014-04-02 13:31 ` Laszlo Ersek
2014-04-02 13:31 ` Laszlo Ersek
2014-04-02 14:37 ` [Qemu-devel] " Fabio Fantoni
2014-04-02 16:03 ` Anthony PERARD
2014-04-02 16:03 ` Anthony PERARD
2014-04-02 16:27 ` [Qemu-devel] [Xen-devel] " Ian Campbell
2014-04-02 16:27 ` [Qemu-devel] " Ian Campbell
2014-04-03 8:15 ` Fabio Fantoni
2014-04-03 8:15 ` Fabio Fantoni
2014-04-03 8:45 ` [Qemu-devel] [Xen-devel] " Ian Campbell
2014-04-03 8:45 ` [Qemu-devel] " Ian Campbell
2014-04-03 10:13 ` [Qemu-devel] [Xen-devel] " Fabio Fantoni
2014-04-03 10:13 ` Fabio Fantoni
2014-04-07 9:59 ` [Qemu-devel] " Fabio Fantoni
2014-04-07 9:59 ` [Xen-devel] [Qemu-devel] " Fabio Fantoni
2014-04-07 10:20 ` Christophe Fergeau [this message]
2014-04-07 10:20 ` Christophe Fergeau
2014-04-07 13:19 ` [Qemu-devel] [Spice-devel] [Xen-devel] " Fabio Fantoni
2014-04-07 13:19 ` [Xen-devel] [Qemu-devel] " Fabio Fantoni
2014-04-07 14:25 ` [Qemu-devel] [Spice-devel] [Xen-devel] " Fabio Fantoni
2014-04-07 14:25 ` [Xen-devel] [Qemu-devel] " Fabio Fantoni
2014-04-01 20:05 ` John Baboval
2014-04-02 16:05 ` Anthony PERARD
2014-04-02 16:05 ` Anthony PERARD
2014-04-03 8:20 ` [Qemu-devel] " Fabio Fantoni
2014-04-03 8:20 ` Fabio Fantoni
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=20140407102040.GJ3724@teriyaki.redhat.com \
--to=cfergeau@redhat.com \
--cc=Ian.Campbell@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=fabio.fantoni@m2r.biz \
--cc=lersek@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=spice-devel@lists.freedesktop.org \
--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.