From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:58119) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1USqGk-0001l4-2l for qemu-devel@nongnu.org; Thu, 18 Apr 2013 10:57:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1USqGi-0001mK-PI for qemu-devel@nongnu.org; Thu, 18 Apr 2013 10:57:01 -0400 Received: from mx1.redhat.com ([209.132.183.28]:20772) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1USqGi-0001m5-Dt for qemu-devel@nongnu.org; Thu, 18 Apr 2013 10:57:00 -0400 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r3IEux7s022367 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 18 Apr 2013 10:56:59 -0400 Message-ID: <1366297017.9382.1.camel@thinkpad-t420s> From: Lucas Meneghel Rodrigues Date: Thu, 18 Apr 2013 11:56:57 -0300 In-Reply-To: <516F984C.4080206@redhat.com> References: <1366044563.3206.6.camel@thinkpad-t420s> <516D0048.60703@redhat.com> <1366224595.2041.16.camel@thinkpad-t420s> <516F984C.4080206@redhat.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [BUG latest master] - qemu segfaults when issuing screendump cmd List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: Luiz Capitulino , "qemu-devel@nongnu.org" , Cleber Rosa On Thu, 2013-04-18 at 08:53 +0200, Gerd Hoffmann wrote: > >> 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. Oh, absolutely. An error at least is normal program operation/behavior, so we'll adapt it. It's rather different than a segmentation fault, which is a bug regardless of the circumstances. Thanks, I'll verify and mark the bug as fixed.