From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NwKU4-0005pA-5c for qemu-devel@nongnu.org; Mon, 29 Mar 2010 15:18:48 -0400 Received: from [140.186.70.92] (port=33513 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NwKU2-0005n5-Te for qemu-devel@nongnu.org; Mon, 29 Mar 2010 15:18:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NwKU1-000801-OO for qemu-devel@nongnu.org; Mon, 29 Mar 2010 15:18:46 -0400 Received: from moutng.kundenserver.de ([212.227.17.9]:51476) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NwKU1-0007xh-CZ for qemu-devel@nongnu.org; Mon, 29 Mar 2010 15:18:45 -0400 Received: from stefan by flocke.weilnetz.de with local (Exim 4.71) (envelope-from ) id 1NwKTi-0003Z4-EA for qemu-devel@nongnu.org; Mon, 29 Mar 2010 21:18:26 +0200 From: Stefan Weil Date: Mon, 29 Mar 2010 21:16:51 +0200 Message-Id: <1269890225-13639-1-git-send-email-weil@mail.berlios.de> Subject: [Qemu-devel] Check format specifiers for fprintf like function pointers List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: QEMU Developers fprintf like function pointers are used for log output, especially for cpu / fpu register dumps. When I examined wrong values for an x86_64 target on a i386 host, I noticed that it was caused by wrong format specifiers and that there are more errors of this kind. I could fix some (see list below), but for target-mips some errors remain to be fixed. Regards, Stefan Weil