Re: [Qemu-devel] SLIRP segfault?

[John Snow <jsnow@redhat.com>]

On 09/06/2015 06:44 PM, Samuel Thibault wrote:
> 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
> 

Ah, of course. makes sense. relayed the info and hopefully I'll get some
nicer traces to try and make sense of.

Thanks for taking a peek.

--js