Date: Fri, 7 Oct 2005 11:04:43 +0200 From: Tijl Coosemans <tijl@ulyssis.org> To: freebsd-questions@freebsd.org Cc: brianjohn@fusemail.com, Ian Moore <no-spam@swiftdsl.com.au> Subject: Re: xine / kaffeine core dumps with bus error Message-ID: <200510071104.44400.tijl@ulyssis.org> In-Reply-To: <200510071047.30870.no-spam@swiftdsl.com.au> References: <2393.209.87.176.132.1128438877.fusewebmail-19592@webmail.fusemail.com > <200510061910.48224.tijl@ulyssis.org> <200510071047.30870.no-spam@swiftdsl.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 07 October 2005 03:17, Ian Moore wrote: > On Friday 07 October 2005 02:40, Tijl Coosemans wrote: > > On Wednesday 05 October 2005 01:45, Ian Moore wrote: > > > On Wednesday 05 October 2005 00:44, Brian John wrote: > > > > I think I'm having a similar problem with totem (which uses > > > > xine) and vlc. Can you try installing /usr/ports/multimedia/vlc > > > > and see what that does? If that gives a bus error as well then > > > > I think we might have the same issue. I haven't been able to > > > > find a solution to this yet... > > > > > > Yep, vlc gives a bus error too. Looks like we have the same > > > problem! > > > > I don't know what the exact problem is, but the bus error occurs > > when loading > > "/usr/X11R6/lib/xine/plugins/1.1.0/xineplug_dmx_audio.so". When you > > remove that file or rename it such that there's no longer ".so" in > > the file name, then xine should work. > > It doesn't work for me - it still core dumps and kdump gives a very > similar trace to the previous one: > > I'm not sure how you figured out it was that plugin - I guess you are > having the same problem and that file was appearing in your ktrace? I have the same problem, but I used gdb. I figured I had to learn how to use it sooner or later and had nothing else on my hands yesterday afternoon, so... Anyway, what you can try is open a terminal window and do the following: tijl@kalimero ~% gdb (gdb) file xine Reading symbols from xine...done. (gdb) r Starting program: /usr/X11R6/bin/xine This is xine (X11 gui) - a free video player v0.99.4. (c) 2000-2004 The xine Team. Program received signal SIGBUS, Bus error. [Switching to Thread 1 (LWP 100119)] 0x28576f96 in CzCUBICSPLINE (this=0x285b7bb0) at fastmix.cpp:112 112 for(_LIi=0;_LIi<_LLen;_LIi++) Current language: auto; currently c++ (gdb) shared Symbols already loaded for /usr/X11R6/lib/libXv.so.1 Symbols already loaded for /usr/local/lib/libintl.so.6 Symbols already loaded for /usr/X11R6/lib/libXft.so.2 Symbols already loaded for /usr/local/lib/libfreetype.so.9 Symbols already loaded for /usr/X11R6/lib/libXrender.so.1 Symbols already loaded for /usr/X11R6/lib/libSM.so.6 Symbols already loaded for /usr/X11R6/lib/libICE.so.6 Symbols already loaded for /usr/X11R6/lib/libXinerama.so.1 Symbols already loaded for /usr/X11R6/lib/libXxf86vm.so.1 Symbols already loaded for /usr/local/lib/libpng.so.5 Symbols already loaded for /usr/X11R6/lib/libxine.so.14 Symbols already loaded for /lib/libz.so.2 Symbols already loaded for /usr/local/lib/libiconv.so.3 Symbols already loaded for /usr/X11R6/lib/libXext.so.6 Symbols already loaded for /usr/X11R6/lib/libXtst.so.6 Symbols already loaded for /usr/X11R6/lib/libX11.so.6 Symbols already loaded for /lib/libm.so.3 Symbols already loaded for /usr/lib/libpthread.so.1 Symbols already loaded for /lib/libc.so.5 Symbols already loaded for /usr/X11R6/lib/libfontconfig.so.1 Symbols already loaded for /usr/local/lib/libexpat.so.5 Symbols already loaded for /libexec/ld-elf.so.1 Symbols already loaded for /usr/X11R6/lib/X11/locale/lib/common/xlcDef.so.2 Symbols already loaded for /usr/X11R6/lib/libXcursor.so.1 Symbols already loaded for /usr/X11R6/lib/xine/plugins/1.1.0/xineplug_dmx_audio.so Symbols already loaded for /usr/local/lib/libmodplug.so.0 Symbols already loaded for /usr/lib/libstdc++.so.4 (gdb) c Continuing. Program terminated with signal SIGBUS, Bus error. The program no longer exists. (gdb) q tijl@kalimero ~% As you can see, xineplug_dmx_audio.so is the last plugin loaded before the SIGBUS. Simply removing that file did the trick for me. However, I'm not sure whether there's really a problem with that plugin. The problem could be more fundamental and is perhaps only triggered by that plugin...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200510071104.44400.tijl>