From: Paolo Bonzini <pbonzini@redhat.com>
To: Howard Spoelstra <hsp.cat7@gmail.com>
Cc: qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Bug AioContext polling is not implemented on Windows with qemu-system-ppc.exe
Date: Wed, 21 Mar 2018 14:22:45 +0100 [thread overview]
Message-ID: <035198fa-b9e1-6084-d9c2-4d344e7058d7@redhat.com> (raw)
In-Reply-To: <CABLmASEF+e-h-nKunLd6QrnKaCAiR0d=GJZq9tN+CrvZh5iL7A@mail.gmail.com>
On 21/03/2018 14:13, Howard Spoelstra wrote:
>> Can you get a backtrace on the Windows system? Perhaps by putting a
>> breakpoint in aio_context_set_poll_params.
>>
>> Paolo
>
> I built qemu-master RC0 with --enable-debug. This is what a bt provides:
I am not sure what is happening here, but it is obviously not too
helpful. :( Perhaps "gdb --args qemu-system-ppc.exe ..." is better?
Thanks,
Paolo
> (gdb) attach 9692
> Attaching to program `c:\qemu-master\qemu-system-ppc.exe', process 9692
> [New Thread 9692.0x670]
> [New Thread 9692.0x238c]
> [New Thread 9692.0xb94]
> [New Thread 9692.0x10bc]
> [New Thread 9692.0x90c]
> [New Thread 9692.0x29a0]
> (gdb) thread apply all bt full
>
> Thread 6 (Thread 9692.0x29a0):
> #0 0x00007ff980ec3811 in ?? ()
> No symbol table info available.
> #1 0x00007ff980ef020b in ?? ()
> No symbol table info available.
> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
>
> Thread 5 (Thread 9692.0x90c):
> #0 0x00007ff980ebff04 in ?? ()
> No symbol table info available.
> #1 0x00007ff97d673b7f in ?? ()
> No symbol table info available.
> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
>
> Thread 4 (Thread 9692.0x10bc):
> #0 0x00007ff980ec3794 in ?? ()
> No symbol table info available.
> #1 0x00007ff980e549dd in ?? ()
> No symbol table info available.
> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
>
> Thread 3 (Thread 9692.0xb94):
> #0 0x00007ff980ec3794 in ?? ()
> ---Type <return> to continue, or q <return> to quit---
> No symbol table info available.
> #1 0x00007ff980e549dd in ?? ()
> No symbol table info available.
> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
>
> Thread 2 (Thread 9692.0x238c):
> #0 0x00007ff980ec3794 in ?? ()
> No symbol table info available.
> #1 0x00007ff980e549dd in ?? ()
> No symbol table info available.
> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
>
> Thread 1 (Thread 9692.0x670):
> #0 0x00007ff980ec09d4 in ?? ()
> No symbol table info available.
> #1 0x00007ff97d6ba9c6 in ?? ()
> No symbol table info available.
> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
> (gdb)
>
> Best,
> Howard
>
next prev parent reply other threads:[~2018-03-21 13:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 17:11 [Qemu-devel] Bug AioContext polling is not implemented on Windows with qemu-system-ppc.exe Howard Spoelstra
2018-03-21 11:07 ` Paolo Bonzini
2018-03-21 13:13 ` Howard Spoelstra
2018-03-21 13:22 ` Paolo Bonzini [this message]
2018-03-21 13:29 ` Howard Spoelstra
2018-03-21 15:27 ` Paolo Bonzini
2018-03-21 16:23 ` Howard Spoelstra
2018-03-21 16:25 ` Paolo Bonzini
2018-03-21 16:31 ` Howard Spoelstra
2018-03-21 16:37 ` Paolo Bonzini
2018-03-22 5:19 ` Peter Xu
2018-03-22 8:28 ` Howard Spoelstra
2018-03-22 8:52 ` Peter Xu
2018-03-22 9:14 ` Paolo Bonzini
2018-03-22 10:06 ` Peter Xu
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=035198fa-b9e1-6084-d9c2-4d344e7058d7@redhat.com \
--to=pbonzini@redhat.com \
--cc=hsp.cat7@gmail.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).