Comment # 1 on bug 1078285 from
Created attachment 758085 [details]
bluez_trial5_chroot_gdb.log

able to recreate the problem with an osc build in loop with vm-type kvm as
detailed in the attached bluez_trial5_chroot_gdb.log

the call stack as reported by gdb is:
===
Program terminated with signal SIGABRT, Aborted.
#0  0x00007fffa6d5661c in raise () from /lib64/libc.so.6
(gdb) bt
#0  0x00007fffa6d5661c in raise () from /lib64/libc.so.6
#1  0x00007fffa6d58840 in abort () from /lib64/libc.so.6
#2  0x00007fffa6fd87a4 in g_assertion_message () from
/usr/lib64/libglib-2.0.so.0
#3  0x00007fffa6fd8c94 in g_assertion_message_cmpnum () from
/usr/lib64/libglib-2.0.so.0
#4  0x000000012ace0460 in test_put_req_delay () at
unit/test-gobex-transfer.c:1624
#5  0x00007fffa6fd821c in ?? () from /usr/lib64/libglib-2.0.so.0
#6  0x00007fffa6fd813c in ?? () from /usr/lib64/libglib-2.0.so.0
#7  0x00007fffa6fd8510 in g_test_run_suite () from /usr/lib64/libglib-2.0.so.0
#8  0x00007fffa6fd8560 in g_test_run () from /usr/lib64/libglib-2.0.so.0
#9  0x000000012acd3644 in main (argc=<optimized out>, argv=<optimized out>) at
unit/test-gobex-transfer.c:2410
===


You are receiving this mail because: