From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NHh5V-0000kg-TM for qemu-devel@nongnu.org; Mon, 07 Dec 2009 12:09:29 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NHh5R-0000ft-5R for qemu-devel@nongnu.org; Mon, 07 Dec 2009 12:09:29 -0500 Received: from [199.232.76.173] (port=56257 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NHh5Q-0000fb-Va for qemu-devel@nongnu.org; Mon, 07 Dec 2009 12:09:25 -0500 Received: from mail-fx0-f219.google.com ([209.85.220.219]:61164) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NHh5R-0003d9-0o for qemu-devel@nongnu.org; Mon, 07 Dec 2009 12:09:25 -0500 Received: by fxm19 with SMTP id 19so4670249fxm.17 for ; Mon, 07 Dec 2009 09:09:23 -0800 (PST) Message-ID: <4B1D36BE.9020801@codemonkey.ws> Date: Mon, 07 Dec 2009 11:09:18 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] Permit zero-sized qemu_malloc() & friends References: <4B1D2462.3070000@codemonkey.ws> <4B1D2696.5080003@redhat.com> <4B1D27EE.7060400@codemonkey.ws> <4B1D292D.4010700@redhat.com> <4B1D2B54.40402@codemonkey.ws> <4B1D2CC2.7010806@redhat.com> <4B1D2E2E.6060907@codemonkey.ws> <4B1D2F38.1040604@redhat.com> <4B1D347A.3030102@codemonkey.ws> <4B1D363A.5020200@redhat.com> In-Reply-To: <4B1D363A.5020200@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Kevin Wolf , Paul Brook , Markus Armbruster , qemu-devel@nongnu.org Avi Kivity wrote: > On 12/07/2009 06:59 PM, Anthony Liguori wrote: >> Avi Kivity wrote: >>> What about developers that hit the assert? Do they send patches >>> that fix code that works in production just so they can run in >>> developer mode? >> >> Sounds like a good way to get developers to help convert from >> qemu_malloc() to qemu_new*() :-) >> > > In 0.12? > > My objection was to different behaviour of 0.12 in dev and production > modes. It's a temporary problem that hopefully will be addressed quickly in the 0.13 cycle. Regards, Anthony Liguori