From: Samuel Thibault <samuel.thibault@gnu.org>
To: John Snow <jsnow@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] SLIRP segfault?
Date: Mon, 7 Sep 2015 00:44:10 +0200 [thread overview]
Message-ID: <20150906224410.GS31785@var.home> (raw)
In-Reply-To: <55E73963.8080004@redhat.com>
Hello,
John Snow, le Wed 02 Sep 2015 14:01:07 -0400, a écrit :
> There was a downstream bug filed against qemu-kvm-2.3.1-1.fc22.x86_64
> that appeared to segfault in the AHCI code when trying to install OSX
> Yosemite.
>
> The debug output looked a little strange, so I asked for a new
> stack-trace on an upstream build using --enable-debug to disable
> optimizations.
>
> This trace came back as segfaulting in SLIRP.
This looks even stranger.
gdb) bt full
#0 0x00007ffff5ff4a2f in send () from /lib64/libpthread.so.0
No symbol table info available.
#1 0x000055555589e06d in slirp_send (so=0x7fffe42cc3c0, buf=0x7ffed85747f0, len=0, flags=0) at slirp/slirp.c:900
No locals.
So the segfault would be in a send call with len=0 ??
I'd rather think that the segfault is actually happening in another
thread, and
thread apply all bt full
should be used to get all traces.
Samuel
next prev parent reply other threads:[~2015-09-06 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 18:01 [Qemu-devel] SLIRP segfault? John Snow
2015-09-06 22:44 ` Samuel Thibault [this message]
2015-09-08 14:46 ` John Snow
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=20150906224410.GS31785@var.home \
--to=samuel.thibault@gnu.org \
--cc=jan.kiszka@siemens.com \
--cc=jsnow@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).