On Mon, Jan 16, 2006 at 08:36:30PM +0100, Loïc Minier wrote: > Could the backtrace below be caused by the bug you mentionned? Would > you like that reassigned and / or forwarded to liboil? > > On Tue, Jan 17, 2006, Hongzheng Wang wrote: > > Program received signal SIGSEGV, Segmentation fault. > > [Switching to Thread -1230034000 (LWP 11811)] > > 0xb6bb34f2 in oil_test_check_impl () from /usr/lib/liboil-0.3.so.0 > > (gdb) bt > > #0 0xb6bb34f2 in oil_test_check_impl () from /usr/lib/liboil-0.3.so.0 > > #1 0xb6cb9f5b in gst_videotestsrc_black () > > from /usr/lib/gstreamer-0.8/libgstvideotestsrc.so > > #2 0xb6cb90df in gst_videotestsrc_smpte () > > from /usr/lib/gstreamer-0.8/libgstvideotestsrc.so > > #3 0xb6cb7da7 in gst_videotestsrc_get_type () > > from /usr/lib/gstreamer-0.8/libgstvideotestsrc.so > > #4 0xb762c3ca in gst_pad_call_get_function () > > from /usr/lib/libgstreamer-0.8.so.1
This looks like a lack of debug symbols. gst_videotestsrc_black() is definitely not calling oil_test_check_impl(). Oh yeah. I forgot to mention. Run the app with the environment variable OIL_CPU_FLAGS=0. If it still segfaults, it's probably not a liboil problem. If it doesn't segfault, it likely indicates a bug in the liboil implementation that is being called in the non-OIL_CPU_FLAGS=0 case. dave... -- David Schleef Big Kitten LLC (http://www.bigkitten.com/) -- data acquisition on Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
