[Qemu-devel] SLIRP segfault?

[John Snow <jsnow@redhat.com>]

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.

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1255144
--enable-debug trace: https://bugzilla.redhat.com/attachment.cgi?id=1069114

I don't have OSX to try to reproduce, diagnose and debug. Anyone here
have any thoughts?


===


Here is a paraphrased summary of the problem from reporter Dick Marinus:

'Version: qemu-kvm-2.3.1-1.fc22.x86_64

Steps to Reproduce:
1. Install OS X Yosemite using these instructions
http://www.contrib.andrew.cmu.edu/~somlo/OSXKVM/
2. Do some CPU intensive task like compressing a large file

Actual results:
qemu-kvm crashes with a segmentation failure'



'The backtrace completely changed but it is reproducable using
qemu-2.3.1 compiled with:

'./configure' '--target-list=x86_64-softmmu' '--enable-debug'
'--enable-kvm' '--enable-spice' '--prefix=/home/meeuw/git/qemu/'

print ad->cur_cmd obviously doesn't work for this backtrace.

I've tried qemu (git) master a few weeks ago and it didn't segfault but
OS X crashed (freezed) anyway.'


--js