From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40597) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V47ff-0004Mg-G3 for qemu-devel@nongnu.org; Tue, 30 Jul 2013 07:00:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V47fY-0000An-04 for qemu-devel@nongnu.org; Tue, 30 Jul 2013 07:00:51 -0400 Received: from goliath.siemens.de ([192.35.17.28]:17144) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V47fX-0000Aa-G6 for qemu-devel@nongnu.org; Tue, 30 Jul 2013 07:00:43 -0400 Message-ID: <51F79CD8.7070807@siemens.com> Date: Tue, 30 Jul 2013 13:00:40 +0200 From: Jan Kiszka MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Error handling in cpu_x86_create List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Igor Mammedov Cc: qemu-devel Hi Igor, just noticed by chance that error handling in cpu_x86_create is likely broken after your changes. Any error after cpu = ...object_new() will not properly release the CPU object again nor report NULL to the caller. That means errors should slip through, no? And cpu_x86_init looks similar. Jan -- Siemens AG, Corporate Technology, CT RTC ITP SES-DE Corporate Competence Center Embedded Linux