From: Thomas Huth <1890310@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1890310] Re: Segfault in artist.c:block_move
Date: Thu, 10 Dec 2020 09:00:17 -0000 [thread overview]
Message-ID: <160759081786.15679.1240456863994394832.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 159655836781.5403.11127209005915887374.malonedeb@soybean.canonical.com
Released with QEMU v5.2.0.
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1890310
Title:
Segfault in artist.c:block_move
Status in QEMU:
Fix Released
Bug description:
Hello,
Reproducer:
cat << EOF | ./hppa-softmmu/qemu-system-hppa -m 64 -display none \
-qtest stdio -accel qtest
writeq 0xf8100802 0xff5c651ffffb7c5c
writeq 0xf8100afb 0x25e000000000000
EOF
AddressSanitizer:DEADLYSIGNAL
=================================================================
==12686==ERROR: AddressSanitizer: SEGV on unknown address 0x7f001a540000 (pc 0x55af3a373078 bp 0x7ffc23001a00 sp 0x7ffc23001670 T0)
==12686==The signal is caused by a READ memory access.
#0 0x55af3a373078 in block_move /hw/display/artist.c:525:13
#1 0x55af3a365fbc in artist_reg_write /hw/display/artist.c:964:9
#2 0x55af39a577a3 in memory_region_write_accessor /softmmu/memory.c:483:5
#3 0x55af39a56adc in access_with_adjusted_size /softmmu/memory.c:539:18
#4 0x55af39a54873 in memory_region_dispatch_write /softmmu/memory.c:1466:16
#5 0x55af39102056 in flatview_write_continue /exec.c:3176:23
#6 0x55af390ea866 in flatview_write /exec.c:3216:14
#7 0x55af390ea387 in address_space_write /exec.c:3308:18
#8 0x55af39afe604 in qtest_process_command /softmmu/qtest.c:452:13
#9 0x55af39af5c08 in qtest_process_inbuf /softmmu/qtest.c:710:9
#10 0x55af39af4895 in qtest_read /softmmu/qtest.c:722:5
#11 0x55af3bfb0c43 in qemu_chr_be_write_impl /chardev/char.c:188:9
#12 0x55af3bfb0dc7 in qemu_chr_be_write /chardev/char.c:200:9
#13 0x55af3bfc50b3 in fd_chr_read /chardev/char-fd.c:68:9
#14 0x55af3c119474 in qio_channel_fd_source_dispatch /io/channel-watch.c:84:12
#15 0x7f0028f60897 in g_main_context_dispatch (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x4e897)
#16 0x55af3c51137b in glib_pollfds_poll /util/main-loop.c:217:9
#17 0x55af3c50eaab in os_host_main_loop_wait /util/main-loop.c:240:5
#18 0x55af3c50e444 in main_loop_wait /util/main-loop.c:516:11
#19 0x55af39b16d00 in qemu_main_loop /softmmu/vl.c:1676:9
#20 0x55af3c151261 in main /softmmu/main.c:49:5
#21 0x7f0027ae6e0a in __libc_start_main /build/glibc-GwnBeO/glibc-2.30/csu/../csu/libc-start.c:308:16
#22 0x55af38ff5729 in _start (/home/alxndr/Development/qemu/general-fuzz/build/hppa-softmmu/qemu-system-hppa+0x22d4729)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV /hw/display/artist.c:525:13 in block_move
==12686==ABORTING
The error occurs even with Message-Id:
<20200804140056.7690-1-deller@gmx.de> applied (I collected the above
trace with the patch-set applied)
Thanks
-Alex
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1890310/+subscriptions
prev parent reply other threads:[~2020-12-10 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 16:26 [Bug 1890310] [NEW] Segfault in artist.c:block_move Alexander Bulekov
2020-08-04 19:54 ` [Bug 1890310] " Helge Deller
2020-10-22 14:27 ` Philippe Mathieu-Daudé
2020-12-10 9:00 ` Thomas Huth [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=160759081786.15679.1240456863994394832.malone@chaenomeles.canonical.com \
--to=1890310@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).