Received: from eggs.gnu.org ([209.51.188.92]:37194) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hKNoz-0003HP-Co for qemu-devel@nongnu.org; Sat, 27 Apr 2019 09:56:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hKNoy-0001bU-9u for qemu-devel@nongnu.org; Sat, 27 Apr 2019 09:56:53 -0400 Received: from mx1.redhat.com ([209.132.183.28]:49602) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hKNoy-0001ZY-20 for qemu-devel@nongnu.org; Sat, 27 Apr 2019 09:56:52 -0400 From: =?UTF-8?q?Philippe=20Mathieu-Daud=C3=A9?= Date: Sat, 27 Apr 2019 15:56:42 +0200 Message-Id: <20190427135642.16464-1-philmd@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: [Qemu-devel] [PATCH] qom/object: Display more helpful message when an object type is missing List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eduardo Habkost , qemu-devel@nongnu.org Cc: =?UTF-8?q?Andreas=20F=C3=A4rber?= , =?UTF-8?q?Daniel=20P=20=2E=20Berrang=C3=A9?= , Eric Blake , Markus Armbruster , =?UTF-8?q?Philippe=20Mathieu-Daud=C3=A9?= When writing a new board, adding device which uses other devices (container) or simply refactoring, one can discover the hard way his machine misses some devices. In the case of containers, the error is not obvious: $ qemu-system-microblaze -M xlnx-zynqmp-pmu ** ERROR:/source/qemu/qom/object.c:454:object_initialize_with_type: assert= ion failed: (type !=3D NULL) Aborted (core dumped) And we have to look at the coredump to figure the error: (gdb) bt #1 0x00007f84773cf895 in abort () at /lib64/libc.so.6 #2 0x00007f847961fb53 in () at /lib64/libglib-2.0.so.0 #3 0x00007f847967a4de in g_assertion_message_expr () at /lib64/libglib= -2.0.so.0 #4 0x000055c4bcac6c11 in object_initialize_with_type (data=3Ddata@entr= y=3D0x55c4bdf239e0, size=3Dsize@entry=3D2464, type=3D) at = /source/qemu/qom/object.c:454 #5 0x000055c4bcac6e6d in object_initialize (data=3Ddata@entry=3D0x55c4= bdf239e0, size=3Dsize@entry=3D2464, typename=3Dtypename@entry=3D0x55c4bcc= 7c643 "xlnx.zynqmp_ipi") at /source/qemu/qom/object.c:474 #6 0x000055c4bc9ea474 in xlnx_zynqmp_pmu_init (machine=3D0x55c4bdd4600= 0) at /source/qemu/hw/microblaze/xlnx-zynqmp-pmu.c:176 #7 0x000055c4bca3b6cb in machine_run_board_init (machine=3D0x55c4bdd46= 000) at /source/qemu/hw/core/machine.c:1030 #8 0x000055c4bc95f6d2 in main (argc=3D, argv=3D, envp=3D) at /source/qemu/vl.c:4479 Since the caller knows the type name requested, we can simply display it to ease development. With this patch applied we get: $ qemu-system-microblaze -M xlnx-zynqmp-pmu qemu-system-microblaze: missing object type 'xlnx.zynqmp_ipi' Aborted (core dumped) Since the assert(type) check in object_initialize_with_type() is now impossible, remove it. Signed-off-by: Philippe Mathieu-Daud=C3=A9 --- qom/object.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/qom/object.c b/qom/object.c index e3206d6799e..b1ba62c5b9e 100644 --- a/qom/object.c +++ b/qom/object.c @@ -28,6 +28,7 @@ #include "qapi/qmp/qbool.h" #include "qapi/qmp/qnum.h" #include "qapi/qmp/qstring.h" +#include "qemu/error-report.h" =20 #define MAX_INTERFACES 32 =20 @@ -451,7 +452,6 @@ static void object_initialize_with_type(void *data, s= ize_t size, TypeImpl *type) { Object *obj =3D data; =20 - g_assert(type !=3D NULL); type_initialize(type); =20 g_assert(type->instance_size >=3D sizeof(Object)); @@ -471,6 +471,11 @@ void object_initialize(void *data, size_t size, cons= t char *typename) { TypeImpl *type =3D type_get_by_name(typename); =20 + if (!type) { + error_report("missing object type '%s'", typename); + abort(); + } + object_initialize_with_type(data, size, type); } =20 --=20 2.20.1