This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [patch] calloc arguments

To: Hollis Blanchard <hollisb@xxxxxxxxxx>
Subject: Re: [Xen-devel] [patch] calloc arguments
From: Anthony Liguori <aliguori@xxxxxxxxxx>
Date: Mon, 17 Apr 2006 18:19:38 -0500
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 17 Apr 2006 16:20:12 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1145307019.16042.110.camel@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1145307019.16042.110.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mail/News 1.5 (X11/20060309)
Hollis Blanchard wrote:
Hi, it looks like a few users of calloc had their arguments backwards. I
checked the other users and they seem fine.

Since one of those is in ioemu code, does that mean we (I?) will be
submitting that bug to qemu upstream?

The bug isn't present in upstream QEmu as this file isn't present. I imagine this is part of the VNC patch that lives externally to QEmu.

In general, QEmu does not use any calloc()'s and instead prefers to use a malloc wrapper (qemu_mallocz) within the actual emulator.


Anthony Liguori

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>