Public bug reported:

When running in a VM (but not on my host system), the bluez-qt
autopkgtests fail with a floating point exception.  The original
failure, affecting both amd64 and i386, can be found here:
http://autopkgtest.ubuntu.com/packages/b/bluez-qt/xenial/amd64/

To reproduce, build bluez-qt from source and then run:

xvfb-run -a --server-args="-screen 0 1024x768x24+32"     sh -c 'cd
obj-*/autotests; gdb ./qmltests'

Thread 1 "qmltests" received signal SIGFPE, Arithmetic exception.
0x00007ffff68fef49 in pthread_barrier_destroy (barrier=0x6aff30)
    at pthread_barrier_destroy.c:39
39      pthread_barrier_destroy.c: No such file or directory.
(gdb) thread apply all bt full

Thread 1 (Thread 0x7ffff7e788c0 (LWP 20087)):
#0  0x00007ffff68fef49 in pthread_barrier_destroy (barrier=0x6aff30)
    at pthread_barrier_destroy.c:39
        bar = 0x6aff30
        count = 0
        max_in_before_reset = <optimized out>
        in = <optimized out>
#1  0x00007fffea1c0f8f in ?? ()
   from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
No symbol table info available.
#2  0x00007fffea1cca61 in ?? ()
   from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
No symbol table info available.
#3  0x00007fffe9e65e6f in ?? ()
   from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
No symbol table info available.
#4  0x00007fffe9e65f15 in ?? ()
   from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
No symbol table info available.
#5  0x00007fffe9e6434f in ?? ()
   from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
No symbol table info available.
#6  0x00007ffff2c82482 in ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
No symbol table info available.
#7  0x00007ffff2c5e466 in ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
No symbol table info available.
#8  0x00007ffff2c5e4e9 in ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
No symbol table info available.
#9  0x00007ffff2c5e63e in ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
No symbol table info available.
#10 0x00007ffff334f642 in XCloseDisplay ()
   from /usr/lib/x86_64-linux-gnu/libX11.so.6
No symbol table info available.
#11 0x00007fffed99c426 in QXcbConnection::~QXcbConnection() ()
   from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
No symbol table info available.
#12 0x00007fffed99c789 in QXcbConnection::~QXcbConnection() ()
   from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
No symbol table info available.
#13 0x00007fffed99ded6 in QXcbIntegration::~QXcbIntegration() ()
   from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
No symbol table info available.
#14 0x00007fffed99dfe9 in QXcbIntegration::~QXcbIntegration() ()
   from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
No symbol table info available.
#15 0x00007ffff557acf3 in QGuiApplicationPrivate::~QGuiApplicationPrivate() ()
   from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
No symbol table info available.
#16 0x00007ffff557aed9 in QGuiApplicationPrivate::~QGuiApplicationPrivate() ()
   from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
No symbol table info available.
#17 0x00007ffff7515db8 in QObject::~QObject() ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
No symbol table info available.
#18 0x00007ffff557ab69 in QGuiApplication::~QGuiApplication() ()
   from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
No symbol table info available.
#19 0x00007ffff7fa1628 in quick_test_main(int, char**, char const*, char 
const*) () from /usr/lib/x86_64-linux-gnu/libQt5QuickTest.so.5
No symbol table info available.
#20 0x000000000040929f in main (argc=1, argv=0x7fffffffe4c8)
    at ../../autotests/qmltests.cpp:105
        testsDir = @0x7fffffffe3a0: {static null = {<No data fields>}, 
          d = 0x635970}
(gdb) 

Since the problem is not reproducible on the host system, current guess
is that it's related to cpu featureset passthrough on the guest.
/proc/cpuinfo from an affected guest:

# cat /proc/cpuinfo 
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 2
model name      : QEMU Virtual CPU version 0.14
stepping        : 3
microcode       : 0x1
cpu MHz         : 2594.108
cache size      : 4096 KB
physical id     : 0
siblings        : 1
core id         : 0
cpu cores       : 1
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 4
wp              : yes
flags           : fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pse36 clflush mmx fxsr sse sse2 syscall nx lm rep_good nopl pni vmx cx16 popcnt 
hypervisor lahf_lm tpr_shadow vnmi flexpriority ept
bogomips        : 5188.21
clflush size    : 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management:
#

It could also be related to the use of swrast_dri rather than a
hardware-accelerated video driver.

** Affects: glibc (Ubuntu)
     Importance: Critical
         Status: Triaged

** Affects: glibc (Ubuntu Xenial)
     Importance: Critical
         Status: Triaged

** Changed in: glibc (Ubuntu)
   Importance: Undecided => Critical

** Changed in: glibc (Ubuntu)
       Status: New => Triaged

** Changed in: glibc (Ubuntu)
    Milestone: None => ubuntu-16.03

** Also affects: glibc (Ubuntu Xenial)
   Importance: Critical
       Status: Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559842

Title:
  SIGFPE in pthread_barrier_destroy in glibc 2.23

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1559842/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to