From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58954) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ahyQj-00064C-Af for qemu-devel@nongnu.org; Mon, 21 Mar 2016 07:57:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ahyNw-0001tP-Bv for qemu-devel@nongnu.org; Mon, 21 Mar 2016 07:55:29 -0400 Received: from mx1.redhat.com ([209.132.183.28]:37080) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ahyNw-0001tJ-4Q for qemu-devel@nongnu.org; Mon, 21 Mar 2016 07:52:36 -0400 From: Markus Armbruster References: <1458320487-19603-1-git-send-email-armbru@redhat.com> <87zits5eo6.fsf@blackfin.pond.sub.org> Date: Mon, 21 Mar 2016 12:52:33 +0100 In-Reply-To: (Peter Maydell's message of "Mon, 21 Mar 2016 10:18:15 +0000") Message-ID: <87wpow3v5q.fsf@blackfin.pond.sub.org> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Qemu-devel] [PULL 00/40] ivshmem: Fixes, cleanups, device model split List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: QEMU Developers Peter Maydell writes: > On 21 March 2016 at 10:05, Markus Armbruster wrote: >> Peter Maydell writes: >>> Also some new clang ubsan warnings on x86 Linux: >>> GTESTER check-qtest-i386 >>> [deleted existing warnings about slirp code] >>> /home/petmay01/linaro/qemu-for-merges/hw/pci/pci.c:166:23: runtime >>> error: shift exponent -1 is negative >>> /home/petmay01/linaro/qemu-for-merges/hw/pci/pci.c:171:24: runtime >>> error: shift exponent -1 is negative >>> /home/petmay01/linaro/qemu-for-merges/hw/pci/pci.c:172:24: runtime >>> error: shift exponent -1 is negative >> >> Stack backtrace? If it's not too much trouble... > > Sorry, too painful -- this version of clang doesn't support > the UBSAN_OPTIONS environment variable to request a backtrace > at runtime and I can't remember the rune to connect gdb to > the qemu under a qtest test, which is what I'd need to do if > I rebuilt everything with the trap-on-error flag. > > The issues are all provoked by the i386/ivshmem/single test. No worries, I reproduced it locally.