|
| From: | Peter Maydell |
| Subject: | Re: [Qemu-devel] [PULL 00/40] ivshmem: Fixes, cleanups, device model split |
| Date: | Mon, 21 Mar 2016 10:18:15 +0000 |
On 21 March 2016 at 10:05, Markus Armbruster <address@hidden> wrote: > Peter Maydell <address@hidden> 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. thanks -- PMM
| [Prev in Thread] | Current Thread | [Next in Thread] |