From: Gerd Hoffmann <kraxel@redhat.com>
To: Lucas Meneghel Rodrigues <lmr@redhat.com>
Cc: Luiz Capitulino <lcapitulino@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Cleber Rosa <crosa@redhat.com>
Subject: Re: [Qemu-devel] [BUG latest master] - qemu segfaults when issuing screendump cmd
Date: Thu, 18 Apr 2013 08:53:00 +0200 [thread overview]
Message-ID: <516F984C.4080206@redhat.com> (raw)
In-Reply-To: <1366224595.2041.16.camel@thinkpad-t420s>
>> Can you try this?
>> git://git.kraxel.org/qemu rebase/pixman
>>
> With current master, qemu crashes.
FYI: pull req sent, anthony merged, so it is fixed in master now.
autotest might need adaptions nevertheless, on headless configurations
(-vga none) qemu starts throwing errors now (due to lack of a screen it
can dump from) instead of silently doing nothing.
cheers,
Gerd
next prev parent reply other threads:[~2013-04-18 6:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 16:49 [Qemu-devel] [BUG latest master] - qemu segfaults when issuing screendump cmd Lucas Meneghel Rodrigues
2013-04-16 7:39 ` Gerd Hoffmann
2013-04-17 18:49 ` Lucas Meneghel Rodrigues
2013-04-18 6:53 ` Gerd Hoffmann [this message]
2013-04-18 14:56 ` Lucas Meneghel Rodrigues
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=516F984C.4080206@redhat.com \
--to=kraxel@redhat.com \
--cc=crosa@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=lmr@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 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.