Re: xine / kaffeine core dumps with bus error
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: [EMAIL PROTECTED] ~% 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 [EMAIL PROTECTED] ~% 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... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xine / kaffeine core dumps with bus error
On Friday 07 October 2005 18:34, you wrote: 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: [EMAIL PROTECTED] ~% 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. To do this, I need to use a kernel build with debugging turned on - correct? I guess it's time I learnt how to do this stuff too, so perhaps I'll give it a go next week when I have some time. I can always keep the debug kernel around for doing this then just boot with it when necessary. 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... Perhaps I'll find something different when I do it, since my problem doesn't appear to be related to the plugins. Cheers, -- Ian gpg key: http://home.swiftdsl.com.au/~imoore/no-spam.asc pgpGcG8UMV4cb.pgp Description: PGP signature
Re: xine / kaffeine core dumps with bus error
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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xine / kaffeine core dumps with bus error
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: 37294 xine RET read 4096/0x1000 37294 xine CALL mmap(0,0x5e000,0x5,0x20002,0x6,0,0,0) 37294 xine RET mmap 704172032/0x29f8d000 37294 xine CALL mprotect(0x29fbb000,0x1000,0x7) 37294 xine RET mprotect 0 37294 xine CALL mprotect(0x29fbb000,0x1000,0x5) 37294 xine RET mprotect 0 37294 xine CALL mmap(0x29fbc000,0x3000,0x3,0x12,0x6,0,0x2e000,0) 37294 xine RET mmap 704364544/0x29fbc000 37294 xine CALL mmap(0x29fbf000,0x2c000,0x3,0x1012,0x,0,0,0) 37294 xine RET mmap 704376832/0x29fbf000 37294 xine CALL close(0x6) 37294 xine RET close 0 37294 xine CALL access(0x2816a000,0) 37294 xine NAMI /usr/X11R6/lib/libstdc++.so.4 37294 xine RET access -1 errno 2 No such file or directory 37294 xine CALL access(0x2816a000,0) 37294 xine NAMI /usr/local/lib/libstdc++.so.4 37294 xine RET access -1 errno 2 No such file or directory 37294 xine CALL access(0x2816a000,0) 37294 xine NAMI /lib/libstdc++.so.4 37294 xine RET access -1 errno 2 No such file or directory 37294 xine CALL access(0x2816a000,0) 37294 xine NAMI /usr/lib/libstdc++.so.4 37294 xine RET access 0 37294 xine CALL access(0x2816a000,0) 37294 xine NAMI /usr/X11R6/lib/libm.so.3 37294 xine RET access -1 errno 2 No such file or directory 37294 xine CALL access(0x2816a000,0) 37294 xine NAMI /usr/local/lib/libm.so.3 37294 xine RET access -1 errno 2 No such file or directory 37294 xine CALL access(0x2816a000,0) 37294 xine NAMI /lib/libm.so.3 37294 xine RET access 0 37294 xine CALL mprotect(0x29f74000,0xf000,0x7) 37294 xine RET mprotect 0 37294 xine CALL mmap(0,0x348,0x3,0x1000,0x,0,0,0) 37294 xine RET mmap 704557056/0x29feb000 37294 xine CALL munmap(0x29feb000,0x348) 37294 xine RET munmap 0 37294 xine CALL mprotect(0x29f74000,0xf000,0x5) 37294 xine RET mprotect 0 37294 xine CALL mmap(0,0xb48,0x3,0x1000,0x,0,0,0) 37294 xine RET mmap 704557056/0x29feb000 37294 xine CALL munmap(0x29feb000,0xb48) 37294 xine RET munmap 0 37294 xine PSIG SIGBUS SIG_DFL 37294 xine CALL kse_thr_interrupt(0,0x4,0xa) 37294 xine NAMI xine.core 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? Just in case there was some cruft in my plugins, I tried moving the whole 1.1.0 dir somewhere else and rebuilt libxine and xine. Then I tried running xine again and it crashed with the same trace as before. Cheers, -- Ian gpg key: http://home.swiftdsl.com.au/~imoore/no-spam.asc pgpMkd8gONjD0.pgp Description: PGP signature
xine / kaffeine core dumps with bus error
Hi, I went to play a video file today with kaffeine and it crashed when trying to open the file. I decided to do a portupgrade -fR kaffeine\* to rebuild it and it's dependencies in the hope that would fix the problem, but it made no difference. Then I tried running xine by itself and found it gave a bus error and core dumped every time I tried to start it (not opening a file or anything). The splash screen appears, then the GUI, then both close and in the xterm I start it from, I just bus error. I've tried doing a portupgrade -f xine just in case, though it should have been re-built along with kaffeine. None of the above seems to fix the problem. I'm running FBSD 5.4-RELEASE p6 and my ports tree was updated last night. Port versions are: kaffeine-0.7.1 xine-0.99.4 Xine/Kaffeine used to work, evidently a recent portupgrade has broken it, though I'm not sure exactly when it last worked. Just hoping someone can suggest a fix! Cheers, -- Ian gpg key: http://home.swiftdsl.com.au/~imoore/no-spam.asc pgpHdsvsqpzVP.pgp Description: PGP signature
Re: xine / kaffeine core dumps with bus error
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... /Brian - Original Message - Hi, I went to play a video file today amp; with kaffeine and it crashed when trying to open the file. I decided to do a portupgrade -fR kaffeine\* to rebuild it and it's dependencies in the hope that would fix the problem, but it made no difference. Then I tried running xine by itself and found it gave a bus error and core dumped every time I tried to start it (not opening a file or anything). The splash screen appears, then the GUI, then both close and in the xterm I start it from, I just bus error. I've tried doing a portupgrade -f xine just in case, though it should have been re-built along with kaffeine. None of the above seems to fix the problem. I'm running FBSD 5.4-RELEASE p6 and my ports tree was updated last night. Port versions are: kaffeine-0.7.1 xine-0.99.4 Xine/Kaffeine used to work, evidently a recent portupgrade has broken it, though I'm not sure exactly when it last worked. Just hoping someone can suggest a fix! Cheers, -- Ian gpg key: http://home.swiftdsl.com.au/~imoore/no-spam.asc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xine / kaffeine core dumps with bus error
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... /Brian Yep, vlc gives a bus error too. Looks like we have the same problem! Cheers, Ian - Original Message - Hi, I went to play a video file today amp; with kaffeine and it crashed when trying to open the file. I decided to do a portupgrade -fR kaffeine\* to rebuild it and it's dependencies in the hope that would fix the problem, but it made no difference. Then I tried running xine by itself and found it gave a bus error and core dumped every time I tried to start it (not opening a file or anything). The splash screen appears, then the GUI, then both close and in the xterm I start it from, I just bus error. I've tried doing a portupgrade -f xine just in case, though it should have been re-built along with kaffeine. None of the above seems to fix the problem. I'm running FBSD 5.4-RELEASE p6 and my ports tree was updated last night. Port versions are: kaffeine-0.7.1 xine-0.99.4 Xine/Kaffeine used to work, evidently a recent portupgrade has broken it, though I'm not sure exactly when it last worked. Just hoping someone can suggest a fix! Cheers, -- Ian gpg key: http://home.swiftdsl.com.au/~imoore/no-spam.asc pgp9bCoo38VFU.pgp Description: PGP signature
Re: xine / kaffeine core dumps with bus error
On 10/4/05, Ian Moore [EMAIL PROTECTED] 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... /Brian Yep, vlc gives a bus error too. Looks like we have the same problem! Cheers, Ian I've found that installing from ports doesn't always (ever? I'm not sure) upgrade the dependencies. Could it be a common shared library used by the three programs? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xine / kaffeine core dumps with bus error
David Kirchner wrote: On 10/4/05, Ian Moore [EMAIL PROTECTED] 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... /Brian Yep, vlc gives a bus error too. Looks like we have the same problem! Cheers, Ian I've found that installing from ports doesn't always (ever? I'm not sure) upgrade the dependencies. Could it be a common shared library used by the three programs? It probably is. However, I'm not sure how to go about figuring out which one of these dependencies it is, let alone how to fix it. Could you help us troubleshoot this? BTW, I used portmanager to upgrade my ports. Thanks /Brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xine / kaffeine core dumps with bus error
On 10/4/05, Brian John [EMAIL PROTECTED] wrote: It probably is. However, I'm not sure how to go about figuring out which one of these dependencies it is, let alone how to fix it. Could you help us troubleshoot this? BTW, I used portmanager to upgrade my ports. I don't know if I can be much help, as I haven't used xine or vlc, or portmanager. What I would do in your case is run 'ktrace -i -d vlc' (along with whatever other arguments) to trace the process and its dependencies, and then run 'kdump' to view the trace (the output will be enormous). You might see something interesting near the end, like a file not found that it was expecting, or it opening a file just prior to dumping core. It may be possible the other programs would have the same last few lines. This is generic advice, I'm afraid, and may not even be valid in this case. But who knows. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xine / kaffeine core dumps with bus error
David Kirchner wrote: On 10/4/05, Brian John [EMAIL PROTECTED] wrote: It probably is. However, I'm not sure how to go about figuring out which one of these dependencies it is, let alone how to fix it. Could you help us troubleshoot this? BTW, I used portmanager to upgrade my ports. I don't know if I can be much help, as I haven't used xine or vlc, or portmanager. What I would do in your case is run 'ktrace -i -d vlc' (along with whatever other arguments) to trace the process and its dependencies, and then run 'kdump' to view the trace (the output will be enormous). You might see something interesting near the end, like a file not found that it was expecting, or it opening a file just prior to dumping core. It may be possible the other programs would have the same last few lines. This is generic advice, I'm afraid, and may not even be valid in this case. But who knows. David, Ok, I sent the logs to you but the list rejected it. I couldn't find anything in there that looked useful. Could this possibly have something to do with the video card I'm running? I'm running a Radeon 9200 SE 256 MB. Ian, What kind of card are you running? Thanks /Brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xine / kaffeine core dumps with bus error
Brian John wrote: David Kirchner wrote: On 10/4/05, Brian John [EMAIL PROTECTED] wrote: It probably is. However, I'm not sure how to go about figuring out which one of these dependencies it is, let alone how to fix it. Could you help us troubleshoot this? BTW, I used portmanager to upgrade my ports. I don't know if I can be much help, as I haven't used xine or vlc, or portmanager. What I would do in your case is run 'ktrace -i -d vlc' (along with whatever other arguments) to trace the process and its dependencies, and then run 'kdump' to view the trace (the output will be enormous). You might see something interesting near the end, like a file not found that it was expecting, or it opening a file just prior to dumping core. It may be possible the other programs would have the same last few lines. This is generic advice, I'm afraid, and may not even be valid in this case. But who knows. David, Ok, I sent the logs to you but the list rejected it. I couldn't find anything in there that looked useful. Could this possibly have something to do with the video card I'm running? I'm running a Radeon 9200 SE 256 MB. Ian, What kind of card are you running? Thanks /Brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Another note: just for the hell of it I installed xine and tried to run it directly -- it didn't crash! So maybe our problems aren't the same after all... /Brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xine / kaffeine core dumps with bus error
On Wednesday 05 October 2005 11:25, David Kirchner wrote: On 10/4/05, Brian John [EMAIL PROTECTED] wrote: It probably is. However, I'm not sure how to go about figuring out which one of these dependencies it is, let alone how to fix it. Could you help us troubleshoot this? BTW, I used portmanager to upgrade my ports. I don't know if I can be much help, as I haven't used xine or vlc, or portmanager. What I would do in your case is run 'ktrace -i -d vlc' (along with whatever other arguments) to trace the process and its dependencies, and then run 'kdump' to view the trace (the output will be enormous). You might see something interesting near the end, like a file not found that it was expecting, or it opening a file just prior to dumping core. It may be possible the other programs would have the same last few lines. This is generic advice, I'm afraid, and may not even be valid in this case. But who knows. OK, I've done that for xine, here's the last bit: 1935 xine RET read 4096/0x1000 1935 xine CALL mmap(0,0x5e000,0x5,0x20002,0x6,0,0,0) 1935 xine RET mmap 692838400/0x294be000 1935 xine CALL mprotect(0x294ec000,0x1000,0x7) 1935 xine RET mprotect 0 1935 xine CALL mprotect(0x294ec000,0x1000,0x5) 1935 xine RET mprotect 0 1935 xine CALL mmap(0x294ed000,0x3000,0x3,0x12,0x6,0,0x2e000,0) 1935 xine RET mmap 693030912/0x294ed000 1935 xine CALL mmap(0x294f,0x2c000,0x3,0x1012,0x,0,0,0) 1935 xine RET mmap 693043200/0x294f 1935 xine CALL close(0x6) 1935 xine RET close 0 1935 xine CALL access(0x2816a000,0) 1935 xine NAMI /usr/X11R6/lib/libstdc++.so.4 1935 xine RET access -1 errno 2 No such file or directory 1935 xine CALL access(0x2816a000,0) 1935 xine NAMI /usr/local/lib/libstdc++.so.4 1935 xine RET access -1 errno 2 No such file or directory 1935 xine CALL access(0x2816a000,0) 1935 xine NAMI /lib/libstdc++.so.4 1935 xine RET access -1 errno 2 No such file or directory 1935 xine CALL access(0x2816a000,0) 1935 xine NAMI /usr/lib/libstdc++.so.4 1935 xine RET access 0 1935 xine CALL access(0x2816a000,0) 1935 xine NAMI /usr/X11R6/lib/libm.so.3 1935 xine RET access -1 errno 2 No such file or directory 1935 xine CALL access(0x2816a000,0) 1935 xine NAMI /usr/local/lib/libm.so.3 1935 xine RET access -1 errno 2 No such file or directory 1935 xine CALL access(0x2816a000,0) 1935 xine NAMI /lib/libm.so.3 1935 xine RET access 0 1935 xine CALL mprotect(0x294ae000,0xf000,0x7) 1935 xine RET mprotect 0 1935 xine CALL mmap(0,0x348,0x3,0x1000,0x,0,0,0) 1935 xine RET mmap 693223424/0x2951c000 1935 xine CALL munmap(0x2951c000,0x348) 1935 xine RET munmap 0 1935 xine CALL mprotect(0x294ae000,0xf000,0x5) 1935 xine RET mprotect 0 1935 xine CALL mmap(0,0xb48,0x3,0x1000,0x,0,0,0) 1935 xine RET mmap 693223424/0x2951c000 1935 xine CALL munmap(0x2951c000,0xb48) 1935 xine RET munmap 0 1935 xine PSIG SIGBUS SIG_DFL 1935 xine CALL kse_thr_interrupt(0,0x4,0xa) 1935 xine NAMI xine.core Looks like it can't see lib files that really are there: %ll /lib/libm* -r--r--r-- 1 root wheel 108400 Feb 24 2004 /lib/libm.so.2 -r--r--r-- 1 root wheel 120004 Jul 29 17:38 /lib/libm.so.3 -r--r--r-- 1 root wheel 41096 Jul 29 17:38 /lib/libmd.so.2 %ll /usr/lib/libstdc++.* -r--r--r-- 1 root wheel 1754130 Jul 29 17:39 /usr/lib/libstdc++.a lrwxr-xr-x 1 root wheel 14 Jul 29 17:39 /usr/lib/libstdc++.so - libstdc++.so.4 -r--r--r-- 1 root wheel 881208 Jul 29 17:39 /usr/lib/libstdc++.so.4 So I don't know what's going on there. Cheers, -- Ian gpg key: http://home.swiftdsl.com.au/~imoore/no-spam.asc pgpxBISvR8yol.pgp Description: PGP signature
Re: xine / kaffeine core dumps with bus error
On Wednesday 05 October 2005 12:41, Ian Moore wrote: On Wednesday 05 October 2005 11:25, David Kirchner wrote: On 10/4/05, Brian John [EMAIL PROTECTED] wrote: It probably is. However, I'm not sure how to go about figuring out which one of these dependencies it is, let alone how to fix it. Could you help us troubleshoot this? BTW, I used portmanager to upgrade my ports. I don't know if I can be much help, as I haven't used xine or vlc, or portmanager. What I would do in your case is run 'ktrace -i -d vlc' (along with whatever other arguments) to trace the process and its dependencies, and then run 'kdump' to view the trace (the output will be enormous). You might see something interesting near the end, like a file not found that it was expecting, or it opening a file just prior to dumping core. It may be possible the other programs would have the same last few lines. This is generic advice, I'm afraid, and may not even be valid in this case. But who knows. And vlc gives the same errors too: 6585 vlc RET read 4096/0x1000 6585 vlc CALL mmap(0,0x5e000,0x5,0x20002,0x5,0,0,0) 6585 vlc RET mmap 687357952/0x28f84000 6585 vlc CALL mprotect(0x28fb2000,0x1000,0x7) 6585 vlc RET mprotect 0 6585 vlc CALL mprotect(0x28fb2000,0x1000,0x5) 6585 vlc RET mprotect 0 6585 vlc CALL mmap(0x28fb3000,0x3000,0x3,0x12,0x5,0,0x2e000,0) 6585 vlc RET mmap 687550464/0x28fb3000 6585 vlc CALL mmap(0x28fb6000,0x2c000,0x3,0x1012,0x,0,0,0) 6585 vlc RET mmap 687562752/0x28fb6000 6585 vlc CALL close(0x5) 6585 vlc RET close 0 6585 vlc CALL access(0x28198000,0) 6585 vlc NAMI /lib/libstdc++.so.4 6585 vlc RET access -1 errno 2 No such file or directory 6585 vlc CALL access(0x28198000,0) 6585 vlc NAMI /usr/lib/libstdc++.so.4 6585 vlc RET access 0 6585 vlc CALL access(0x28198000,0) 6585 vlc NAMI /lib/libm.so.3 6585 vlc RET access 0 6585 vlc CALL mmap(0,0x190,0x3,0x1000,0x,0,0,0) 6585 vlc RET mmap 687742976/0x28fe2000 6585 vlc CALL munmap(0x28fe2000,0x190) 6585 vlc RET munmap 0 6585 vlc CALL mmap(0,0xb48,0x3,0x1000,0x,0,0,0) 6585 vlc RET mmap 687742976/0x28fe2000 6585 vlc CALL munmap(0x28fe2000,0xb48) 6585 vlc RET munmap 0 6585 vlc CALL sigprocmask(0x3,0x281882f0,0) 6585 vlc RET sigprocmask 0 6585 vlc PSIG SIGBUS SIG_DFL 6585 vlc NAMI vlc.core -- Ian gpg key: http://home.swiftdsl.com.au/~imoore/no-spam.asc pgpmO1npQljpc.pgp Description: PGP signature
Re: xine / kaffeine core dumps with bus error
On 10/4/05, Ian Moore [EMAIL PROTECTED] wrote: OK, I've done that for xine, here's the last bit: 1935 xine RET read 4096/0x1000 1935 xine CALL mmap(0,0x5e000,0x5,0x20002,0x6,0,0,0) 1935 xine RET mmap 692838400/0x294be000 1935 xine CALL mprotect(0x294ec000,0x1000,0x7) 1935 xine RET mprotect 0 1935 xine CALL mprotect(0x294ec000,0x1000,0x5) 1935 xine RET mprotect 0 1935 xine CALL mmap(0x294ed000,0x3000,0x3,0x12,0x6,0,0x2e000,0) 1935 xine RET mmap 693030912/0x294ed000 1935 xine CALL mmap(0x294f,0x2c000,0x3,0x1012,0x,0,0,0) 1935 xine RET mmap 693043200/0x294f 1935 xine CALL close(0x6) 1935 xine RET close 0 1935 xine CALL access(0x2816a000,0) 1935 xine NAMI /usr/X11R6/lib/libstdc++.so.4 1935 xine RET access -1 errno 2 No such file or directory 1935 xine CALL access(0x2816a000,0) 1935 xine NAMI /usr/local/lib/libstdc++.so.4 1935 xine RET access -1 errno 2 No such file or directory 1935 xine CALL access(0x2816a000,0) 1935 xine NAMI /lib/libstdc++.so.4 1935 xine RET access -1 errno 2 No such file or directory 1935 xine CALL access(0x2816a000,0) 1935 xine NAMI /usr/lib/libstdc++.so.4 1935 xine RET access 0 1935 xine CALL access(0x2816a000,0) 1935 xine NAMI /usr/X11R6/lib/libm.so.3 1935 xine RET access -1 errno 2 No such file or directory 1935 xine CALL access(0x2816a000,0) 1935 xine NAMI /usr/local/lib/libm.so.3 1935 xine RET access -1 errno 2 No such file or directory 1935 xine CALL access(0x2816a000,0) 1935 xine NAMI /lib/libm.so.3 1935 xine RET access 0 1935 xine CALL mprotect(0x294ae000,0xf000,0x7) 1935 xine RET mprotect 0 1935 xine CALL mmap(0,0x348,0x3,0x1000,0x,0,0,0) 1935 xine RET mmap 693223424/0x2951c000 1935 xine CALL munmap(0x2951c000,0x348) 1935 xine RET munmap 0 1935 xine CALL mprotect(0x294ae000,0xf000,0x5) 1935 xine RET mprotect 0 1935 xine CALL mmap(0,0xb48,0x3,0x1000,0x,0,0,0) 1935 xine RET mmap 693223424/0x2951c000 1935 xine CALL munmap(0x2951c000,0xb48) 1935 xine RET munmap 0 1935 xine PSIG SIGBUS SIG_DFL 1935 xine CALL kse_thr_interrupt(0,0x4,0xa) 1935 xine NAMI xine.core Looks like it can't see lib files that really are there: %ll /lib/libm* -r--r--r-- 1 root wheel 108400 Feb 24 2004 /lib/libm.so.2 -r--r--r-- 1 root wheel 120004 Jul 29 17:38 /lib/libm.so.3 -r--r--r-- 1 root wheel 41096 Jul 29 17:38 /lib/libmd.so.2 %ll /usr/lib/libstdc++.* -r--r--r-- 1 root wheel 1754130 Jul 29 17:39 /usr/lib/libstdc++.a lrwxr-xr-x 1 root wheel 14 Jul 29 17:39 /usr/lib/libstdc++.so - libstdc++.so.4 -r--r--r-- 1 root wheel 881208 Jul 29 17:39 /usr/lib/libstdc++.so.4 So I don't know what's going on there. What it's doing there is checking the library path to try and find the requested library -- it does eventually find it, so that's OK. What this ktrace shows is that the dump occurs before anything else goes on -- ie just after loading the initial set of libraries it does something not related to a system call (like mishandling a pointer). I hate to suggest this, especially since you've had world built for so long without trouble, but maybe a freshly updated world would help? libstdc++ hasn't been updated in quite a while, but libm has had some radical changes made to it, it seems. It may not actually mean anything specific, though. I'm stuck at this point, I think. I don't know a lot about the X server internals or the drivers (specifically to the Radeon question). Might be best just to downgrade the port rather than mess around with something as big as rebuilding the entire world. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
