[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] No symbols in LeakSanitizer output (was Re: [RFC PATCH 0/7]
From: |
Eduardo Habkost |
Subject: |
[Qemu-devel] No symbols in LeakSanitizer output (was Re: [RFC PATCH 0/7] target/i386: support VMX features in "-cpu") |
Date: |
Tue, 2 Jul 2019 18:38:24 -0300 |
Can the asan build test in Patchew be updated to include
symbolize=1?
For reference, below is the full stack trace of the leak. It
looks like it existed for a long time.
[qemu/machine-next]$ export ASAN_OPTIONS=symbolize=1
[qemu/machine-next]$ export ASAN_SYMBOLIZER_PATH=/usr/bin/llvm-symbolizer
[qemu/machine-next]$ MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255
+ 1))} QTEST_QEMU_BINARY=x86_64-softmmu/qemu-system-x86_64
QTEST_QEMU_IMG=qemu-img tests/device-introspect-test -m=quick -k --tap <
/dev/null | ./scripts/tap-driver.pl --test-name="qmp-test"
PASS 1 qmp-test /x86_64/device/introspect/list
PASS 2 qmp-test /x86_64/device/introspect/list-fields
PASS 3 qmp-test /x86_64/device/introspect/none
PASS 4 qmp-test /x86_64/device/introspect/abstract
PASS 5 qmp-test /x86_64/device/introspect/abstract-interfaces
=================================================================
==21992==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 32 byte(s) in 1 object(s) allocated from:
#0 0x55e9a04dfc6e in calloc
(/home/ehabkost/rh/proj/virt/qemu/x86_64-softmmu/qemu-system-x86_64+0x18b5c6e)
#1 0x7fb604a10cf0 in g_malloc0 (/lib64/libglib-2.0.so.0+0x55cf0)
#2 0x55e9a1712c0b in gpio_i2c_init
/home/ehabkost/rh/proj/virt/qemu/hw/i2c/bitbang_i2c.c:237:18
#3 0x55e9a23885d8 in object_init_with_type
/home/ehabkost/rh/proj/virt/qemu/qom/object.c:359:9
#4 0x55e9a236e80f in object_initialize_with_type
/home/ehabkost/rh/proj/virt/qemu/qom/object.c:463:5
#5 0x55e9a2370b95 in object_new_with_type
/home/ehabkost/rh/proj/virt/qemu/qom/object.c:632:5
#6 0x55e9a23709b1 in object_new
/home/ehabkost/rh/proj/virt/qemu/qom/object.c:642:12
#7 0x55e9a20b5cc8 in qmp_device_list_properties
/home/ehabkost/rh/proj/virt/qemu/monitor/qmp-cmds.c:528:11
#8 0x55e9a11b5094 in qdev_device_help
/home/ehabkost/rh/proj/virt/qemu/qdev-monitor.c:275:17
#9 0x55e9a11bab2a in qmp_device_add
/home/ehabkost/rh/proj/virt/qemu/qdev-monitor.c:810:34
#10 0x55e9a20e31a1 in hmp_device_add
/home/ehabkost/rh/proj/virt/qemu/monitor/hmp-cmds.c:2169:5
#11 0x55e9a20a2de6 in handle_hmp_command
/home/ehabkost/rh/proj/virt/qemu/monitor/hmp.c:1082:5
#12 0x55e9a0d883af in qmp_human_monitor_command
/home/ehabkost/rh/proj/virt/qemu/monitor/misc.c:139:5
#13 0x55e9a21c4a24 in qmp_marshal_human_monitor_command
/home/ehabkost/rh/proj/virt/qemu/qapi/qapi-commands-misc.c:1172:14
#14 0x55e9a2983c28 in do_qmp_dispatch
/home/ehabkost/rh/proj/virt/qemu/qapi/qmp-dispatch.c:131:5
#15 0x55e9a2982f05 in qmp_dispatch
/home/ehabkost/rh/proj/virt/qemu/qapi/qmp-dispatch.c:174:11
#16 0x55e9a209d2f5 in monitor_qmp_dispatch
/home/ehabkost/rh/proj/virt/qemu/monitor/qmp.c:120:11
#17 0x55e9a209b525 in monitor_qmp_bh_dispatcher
/home/ehabkost/rh/proj/virt/qemu/monitor/qmp.c:209:9
#18 0x55e9a2b1942a in aio_bh_call
/home/ehabkost/rh/proj/virt/qemu/util/async.c:89:5
#19 0x55e9a2b19b42 in aio_bh_poll
/home/ehabkost/rh/proj/virt/qemu/util/async.c:117:13
#20 0x55e9a2b3b800 in aio_dispatch
/home/ehabkost/rh/proj/virt/qemu/util/aio-posix.c:459:5
#21 0x55e9a2b1eb73 in aio_ctx_dispatch
/home/ehabkost/rh/proj/virt/qemu/util/async.c:260:5
#22 0x7fb604a0aedc in g_main_context_dispatch
(/lib64/libglib-2.0.so.0+0x4fedc)
Direct leak of 32 byte(s) in 1 object(s) allocated from:
#0 0x55e9a04dfc6e in calloc
(/home/ehabkost/rh/proj/virt/qemu/x86_64-softmmu/qemu-system-x86_64+0x18b5c6e)
#1 0x7fb604a10cf0 in g_malloc0 (/lib64/libglib-2.0.so.0+0x55cf0)
#2 0x55e9a1712c0b in gpio_i2c_init
/home/ehabkost/rh/proj/virt/qemu/hw/i2c/bitbang_i2c.c:237:18
#3 0x55e9a23885d8 in object_init_with_type
/home/ehabkost/rh/proj/virt/qemu/qom/object.c:359:9
#4 0x55e9a236e80f in object_initialize_with_type
/home/ehabkost/rh/proj/virt/qemu/qom/object.c:463:5
#5 0x55e9a2370b95 in object_new_with_type
/home/ehabkost/rh/proj/virt/qemu/qom/object.c:632:5
#6 0x55e9a23709b1 in object_new
/home/ehabkost/rh/proj/virt/qemu/qom/object.c:642:12
#7 0x55e9a20b5cc8 in qmp_device_list_properties
/home/ehabkost/rh/proj/virt/qemu/monitor/qmp-cmds.c:528:11
#8 0x55e9a21c7624 in qmp_marshal_device_list_properties
/home/ehabkost/rh/proj/virt/qemu/qapi/qapi-commands-misc.c:1439:14
#9 0x55e9a2983c28 in do_qmp_dispatch
/home/ehabkost/rh/proj/virt/qemu/qapi/qmp-dispatch.c:131:5
#10 0x55e9a2982f05 in qmp_dispatch
/home/ehabkost/rh/proj/virt/qemu/qapi/qmp-dispatch.c:174:11
#11 0x55e9a209d2f5 in monitor_qmp_dispatch
/home/ehabkost/rh/proj/virt/qemu/monitor/qmp.c:120:11
#12 0x55e9a209b525 in monitor_qmp_bh_dispatcher
/home/ehabkost/rh/proj/virt/qemu/monitor/qmp.c:209:9
#13 0x55e9a2b1942a in aio_bh_call
/home/ehabkost/rh/proj/virt/qemu/util/async.c:89:5
#14 0x55e9a2b19b42 in aio_bh_poll
/home/ehabkost/rh/proj/virt/qemu/util/async.c:117:13
#15 0x55e9a2b3b800 in aio_dispatch
/home/ehabkost/rh/proj/virt/qemu/util/aio-posix.c:459:5
#16 0x55e9a2b1eb73 in aio_ctx_dispatch
/home/ehabkost/rh/proj/virt/qemu/util/async.c:260:5
#17 0x7fb604a0aedc in g_main_context_dispatch
(/lib64/libglib-2.0.so.0+0x4fedc)
SUMMARY: AddressSanitizer: 64 byte(s) leaked in 2 allocation(s).
tests/libqtest.c:137: kill_qemu() tried to terminate QEMU process but
encountered exit status 1
ERROR - too few tests run (expected 6, got 5)
On Tue, Jul 02, 2019 at 02:13:39PM -0700, address@hidden wrote:
> Patchew URL: https://patchew.org/QEMU/address@hidden/
[...]
> =================================================================
> ==10979==ERROR: LeakSanitizer: detected memory leaks
>
> Direct leak of 32 byte(s) in 1 object(s) allocated from:
> #0 0x558e9bbf3b1e in calloc
> (/tmp/qemu-test/build/x86_64-softmmu/qemu-system-x86_64+0x19f8b1e)
> ---
>
> SUMMARY: AddressSanitizer: 64 byte(s) leaked in 2 allocation(s).
> /tmp/qemu-test/src/tests/libqtest.c:137: kill_qemu() tried to terminate QEMU
> process but encountered exit status 1
> ERROR - too few tests run (expected 6, got 5)
> make: *** [/tmp/qemu-test/src/tests/Makefile.include:894: check-qtest-x86_64]
> Error 1
> make: *** Waiting for unfinished jobs....
> Traceback (most recent call last):
>
>
> The full log is available at
> http://patchew.org/logs/address@hidden/testing.asan/?type=message.
> ---
> Email generated automatically by Patchew [https://patchew.org/].
> Please send your feedback to address@hidden
--
Eduardo
- Re: [Qemu-devel] [PATCH 1/7] target/i386: handle filtered_features in a new function mark_unavailable_features, (continued)
[Qemu-devel] [PATCH 7/7] target/i386: work around KVM_GET_MSRS bug for secondary execution controls, Paolo Bonzini, 2019/07/02
[Qemu-devel] [PATCH 5/7] vmxcap: correct the name of the variables, Paolo Bonzini, 2019/07/02
[Qemu-devel] [PATCH 4/7] target/i386: add VMX definitions, Paolo Bonzini, 2019/07/02
[Qemu-devel] [PATCH 3/7] target/i386: expand feature words to 64 bits, Paolo Bonzini, 2019/07/02
Re: [Qemu-devel] [RFC PATCH 0/7] target/i386: support VMX features in "-cpu", no-reply, 2019/07/02
Re: [Qemu-devel] [RFC PATCH 0/7] target/i386: support VMX features in "-cpu", no-reply, 2019/07/02
- [Qemu-devel] No symbols in LeakSanitizer output (was Re: [RFC PATCH 0/7] target/i386: support VMX features in "-cpu"),
Eduardo Habkost <=