SUMMARY -------- Whilst running the tests for dbus [v1.2.1], the test-segfault application 'quits unexpectedly'. OVERVIEW -------- Configuration and make executed without reporting any errors. STEPS TO REPRODUCE. ------------------ configure make make check ACTUAL RESULTS (OSX crash report). ---------------------------- Thread 0 Crashed: 0 libSystem.B.dylib 0x9241db9e __kill + 10 1 libSystem.B.dylib 0x92494ec2 raise + 26 2 test-segfault 0x00001ff0 main + 96 (test-segfault.c:28) 3 test-segfault 0x00001f56 start + 54 Thread 0 crashed with X86 Thread State (32-bit): eax: 0x00000000 ebx: 0xbffff31c ecx: 0xbffff1cc edx: 0x9241db9e edi: 0x00000000 esi: 0xbffff220 ebp: 0xbffff1e8 esp: 0xbffff1cc ss: 0x0000001f efl: 0x00000282 eip: 0x9241db9e cs: 0x00000007 ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037 cr2: 0xa02223ec Binary Images: 0x1000 - 0x1ffe +test-segfault ??? (???) <630894ae2ced5784a8105998370d6bce> /Volumes/src/src_gnm_base/dbus-1.2.1/test/test-segfault 0x8fe00000 - 0x8fe2da53 dyld 96.2 (???) <06900973e83f70548b7a2a5fa6435865> /usr/lib/dyld 0x923ae000 - 0x9250eff3 libSystem.B.dylib ??? (???) <a12f397abf2285077b89bd726bff5b18> /usr/lib/libSystem.B.dylib 0x96112000 - 0x96116fff libmathCommon.A.dylib ??? (???) /usr/lib/system/libmathCommon.A.dylib 0x96a96000 - 0x96a9dfe9 libgcc_s.1.dylib ??? (???) <f53c808e87d1184c0f9df63aef53ce0b> /usr/lib/libgcc_s.1.dylib 0xffff0000 - 0xffff1780 libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib EXPECTED RESULTS. --------------- pass tests. BUILD AND PLATFORM. ------------------ date: 13 July 2008 platform: Mac OSX 10.5.4/Darwin 9.4.0 ADDITIONAL BUILDS AND PLATFORMS. ------------------------------ unknown. ADDITIONAL INFORMATION. ---------------------- libexpat is installed in two locations, but which is used is unknown (one factory in). packages installed prior to dbus follow the gnome recommended order for a full install. all libraries installed are with the option --disable-static.
I can't reproduce this on 10.6. Can you try with the latest master?
test-segfault.c: /* This is simply a process that segfaults */ so... yeah, it crashes, and that's the expected behaviour (it's to test that we do the right thing if a child process crashes). Does 'make check' exit 0?
Sorry for delay. I'll be getting around to testing this soon. A.
Believed to be a non-bug, please reopen with more information if we've misunderstood.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.