ffmpeg Bus error: 10 (core dumped)
Hi all, I just installed ffmpeg from ports (after a portsnap update). Running ffmpeg results in a core dump: # /usr/local/bin/ffmpeg -i myfile.flv output.flv FFmpeg version 0.6, Copyright (c) 2000-2010 the FFmpeg developers built on Aug 10 2010 14:46:32 with gcc 3.4.6 [FreeBSD] 20060305 configuration: --prefix=/usr/local --mandir=/usr/local/man --enable-shared --enable-gpl --enable-postproc --enable-avfilter --enable-avfilter-lavf --enable-pthreads --enable-x11grab --enable-memalign-hack --cc=cc --extra-cflags=-I/usr/local/include/vorbis -I/usr/local/include --extra-ldflags=-L/usr/local/lib --extra-libs=-pthread --disable-debug --disable-sse --disable-mmx --enable-libopencore-amrnb --enable-version3 --enable-libopencore-amrwb --enable-version3 --disable-libdirac --disable-libfaac --enable-libfaad --enable-libfaadbin --enable-libgsm --enable-libmp3lame --disable-libopenjpeg --disable-libschroedinger --disable-ffplay --disable-libspeex --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxvid libavutil 50.15. 1 / 50.15. 1 libavcodec52.72. 2 / 52.72. 2 libavformat 52.64. 2 / 52.64. 2 libavdevice 52. 2. 0 / 52. 2. 0 libavfilter1.19. 0 / 1.19. 0 libswscale 0.11. 0 / 0.11. 0 libpostproc 51. 2. 0 / 51. 2. 0 Bus error: 10 (core dumped) Here's the backtrace: # gdb `which ffmpeg` ffmpeg.core [...etc, etc] This GDB was configured as "i386-marcel-freebsd"...(no debugging symbols found)... Core was generated by `ffmpeg'. Program terminated with signal 10, Bus error. Reading symbols from /usr/local/lib/libavdevice.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libavdevice.so.1 [...etc, etc] Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x2812ea67 in ff_av_dup_packet () from /usr/local/lib/libavformat.so.1 [New LWP 100870] (gdb) bt #0 0x2812ea67 in ff_av_dup_packet () from /usr/local/lib/libavformat.so.1 Cannot access memory at address 0xbf94 Running FreeBSD 6.3-RELEASE. Any thoughts / suggestions? Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: freecolor: Bus error. software or hardware problem?
So, is it port trouble? -- Best regards, Antonio Kless, http://kless.spb.ru/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: freecolor: Bus error. software or hardware problem?
2010/7/23 Antonio Kless > > > 2010/7/23 Randy Belk > > Have you updated your ports? This was an issue on the amd64 distribution, >> but it was fixed. >> >> On Fri, Jul 23, 2010 at 1:21 AM, Antonio Kless wrote: >> >>> Strange freecolor behavior on fresh 8.0-RELEASE system. >>> >>> # uname -a >>> FreeBSD alternate-1.net 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 >>> 15:02:08 UTC 2009 r...@mason.cse.buffalo.edu: >>> /usr/obj/usr/src/sys/GENERIC >>> amd64 >>> >>> # freecolor -V >>> freecolor version 0.8.8 >>> >>> # freecolor >>> Bus error >>> >>> >>> I have reinstall 7.3-RELEASE on this server, and get another look of >>> error: >>> >>> # freecolor >>> Bus error: 10 >>> >>> >>> Is it software or hardware problem? >>> >>> -- >>> Best regards, >>> Antonio Kless, >>> http://kless.spb.ru/ >>> ___ >>> freebsd-questions@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>> To unsubscribe, send any mail to " >>> freebsd-questions-unsubscr...@freebsd.org" >>> >> >> >> >> -- >> - Simplicity is the ultimate sophistication. - Leonardo da Vinci >> - Intelligence is not defined by what you know, It's how you USE it. >> - People who hate Windows use Linux but people who love UNIX use BSD. >> > > > Yes, I run > # portsnap fetch update > just about 1 hour ago. > > -- > Best regards, > Antonio Kless, > http://kless.spb.ru/ > ...run it before I install freecolor port, of course. -- Best regards, Antonio Kless, http://kless.spb.ru/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: freecolor: Bus error. software or hardware problem?
2010/7/23 Randy Belk > Have you updated your ports? This was an issue on the amd64 distribution, > but it was fixed. > > On Fri, Jul 23, 2010 at 1:21 AM, Antonio Kless wrote: > >> Strange freecolor behavior on fresh 8.0-RELEASE system. >> >> # uname -a >> FreeBSD alternate-1.net 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 >> 15:02:08 UTC 2009 r...@mason.cse.buffalo.edu: >> /usr/obj/usr/src/sys/GENERIC >> amd64 >> >> # freecolor -V >> freecolor version 0.8.8 >> >> # freecolor >> Bus error >> >> >> I have reinstall 7.3-RELEASE on this server, and get another look of >> error: >> >> # freecolor >> Bus error: 10 >> >> >> Is it software or hardware problem? >> >> -- >> Best regards, >> Antonio Kless, >> http://kless.spb.ru/ >> ___ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to " >> freebsd-questions-unsubscr...@freebsd.org" >> > > > > -- > - Simplicity is the ultimate sophistication. - Leonardo da Vinci > - Intelligence is not defined by what you know, It's how you USE it. > - People who hate Windows use Linux but people who love UNIX use BSD. > Yes, I run # portsnap fetch update just about 1 hour ago. -- Best regards, Antonio Kless, http://kless.spb.ru/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: freecolor: Bus error. software or hardware problem?
Have you updated your ports? This was an issue on the amd64 distribution, but it was fixed. On Fri, Jul 23, 2010 at 1:21 AM, Antonio Kless wrote: > Strange freecolor behavior on fresh 8.0-RELEASE system. > > # uname -a > FreeBSD alternate-1.net 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 > 15:02:08 UTC 2009 r...@mason.cse.buffalo.edu: > /usr/obj/usr/src/sys/GENERIC > amd64 > > # freecolor -V > freecolor version 0.8.8 > > # freecolor > Bus error > > > I have reinstall 7.3-RELEASE on this server, and get another look of error: > > # freecolor > Bus error: 10 > > > Is it software or hardware problem? > > -- > Best regards, > Antonio Kless, > http://kless.spb.ru/ > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscr...@freebsd.org" > -- - Simplicity is the ultimate sophistication. - Leonardo da Vinci - Intelligence is not defined by what you know, It's how you USE it. - People who hate Windows use Linux but people who love UNIX use BSD. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
freecolor: Bus error. software or hardware problem?
Strange freecolor behavior on fresh 8.0-RELEASE system. # uname -a FreeBSD alternate-1.net 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC 2009 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 # freecolor -V freecolor version 0.8.8 # freecolor Bus error I have reinstall 7.3-RELEASE on this server, and get another look of error: # freecolor Bus error: 10 Is it software or hardware problem? -- Best regards, Antonio Kless, http://kless.spb.ru/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: apache signal bus error (10)
On Wed, Apr 28, 2010 at 4:26 PM, Greg Larkin wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > doug schmidt wrote: >> On Wed, Apr 28, 2010 at 3:44 PM, Greg Larkin wrote: >>> -BEGIN PGP SIGNED MESSAGE- >>> Hash: SHA1 >>> >>> doug schmidt wrote: >>>> On Wed, Apr 28, 2010 at 1:44 PM, doug schmidt >>>> wrote: >>>>> On Wed, Apr 28, 2010 at 11:28 AM, doug schmidt >>>>> wrote: >>>>>> On Wed, Apr 28, 2010 at 10:23 AM, Greg Larkin >>>>>> wrote: >>>>>>> -BEGIN PGP SIGNED MESSAGE- >>>>>>> Hash: SHA1 >>>>>>> >>>>>>> doug schmidt wrote: >>>>>>>> On a 7.3-release box, I upgraded to php 5.3.2 + extensions. All seems >>>>>>>> [Tue Apr 27 16:08:37 2010] [notice] child pid 37609 exit signal Bus >>>>>>>> error (10) >>>>>>>> >>>>>>> Check out this page: >>>>>>> http://www.pingle.org/2007/09/22/php-crashes-extensions-workaround >>>>>> I'll give the script a try and see. If not, at least I know the >>>>>> specific extension >>>>>> and can test moving the order it is in. >>>>>> >>>>> I've tried using the script, then moving the session.so extension one >>>>> after the other. >>>>> Restarting apache each time and the same bus error. >>>>> >>>>> any other ideas? >>>>> >>>> I now have everything commented out in extensions.ini except for session.so >>>> There is no bus error, so I'll test moving the extensions order some >>>> more. Find it >>>> sooner or later. Real pain, that the order on one box, does not matter >>>> on another >>>> box. >> >>> Do you get a core file anywhere from the Apache process? It would be >>> interesting to get a backtrace so you can figure out what module is >>> causing the problem. >> >> Hi Greg, >> Unfortunately, no core files anywhere. >> >> The problem looks like session.so and mysql.so >> >> With all extensions uncommented, session.so uncommented, mysql.so commented >> out >> no bus error. >> >> All extensions uncommented, mysql.so uncommented, session.so commented out >> no bus error. >> >> All extensions commented out, mysql.so commented out, session.so uncommented >> no bus error. >> >> All extensions commented out, session.so commented out, mysql.so uncommented >> no bus error. >> >> All extensions commented out, session.so and mysql.so uncommented >> bus error. >> >> thanks. >> doug > > Hi Doug, > > What happens if you swap the order of session.so and mysql.so and try > the same tests? From what I see on this page > (http://forums.freebsd.org/archive/index.php/t-927.html), mysql.so > should go before session.so. > > If that results in the same problems, that's when I start firing up the > Apache process with truss to see what's called before the bus error. > You can do that like so: > > truss -f -a -s 256 -o /tmp/apache.log /usr/local/sbin/httpd > > Then reproduce the bus error and stop the main Apache process. > /tmp/apache.log may contain some clues about what the processes were > doing before the crash, especially if you search for "php", "session" or > "mysql" in the file. > Nice. we are in business. apc.so was in extensions.ini but the file was not in the path. I installed pecl-APC. Also, there was a typo in extensions.ini for pgsql thanks for your help. doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: apache signal bus error (10)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 doug schmidt wrote: > On Wed, Apr 28, 2010 at 3:44 PM, Greg Larkin wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> doug schmidt wrote: >>> On Wed, Apr 28, 2010 at 1:44 PM, doug schmidt >>> wrote: >>>> On Wed, Apr 28, 2010 at 11:28 AM, doug schmidt >>>> wrote: >>>>> On Wed, Apr 28, 2010 at 10:23 AM, Greg Larkin wrote: >>>>>> -BEGIN PGP SIGNED MESSAGE- >>>>>> Hash: SHA1 >>>>>> >>>>>> doug schmidt wrote: >>>>>>> On a 7.3-release box, I upgraded to php 5.3.2 + extensions. All seems >>>>>>> [Tue Apr 27 16:08:37 2010] [notice] child pid 37609 exit signal Bus >>>>>>> error (10) >>>>>>> >>>>>> Check out this page: >>>>>> http://www.pingle.org/2007/09/22/php-crashes-extensions-workaround >>>>> I'll give the script a try and see. If not, at least I know the >>>>> specific extension >>>>> and can test moving the order it is in. >>>>> >>>> I've tried using the script, then moving the session.so extension one >>>> after the other. >>>> Restarting apache each time and the same bus error. >>>> >>>> any other ideas? >>>> >>> I now have everything commented out in extensions.ini except for session.so >>> There is no bus error, so I'll test moving the extensions order some >>> more. Find it >>> sooner or later. Real pain, that the order on one box, does not matter >>> on another >>> box. > >> Do you get a core file anywhere from the Apache process? It would be >> interesting to get a backtrace so you can figure out what module is >> causing the problem. > > Hi Greg, > Unfortunately, no core files anywhere. > > The problem looks like session.so and mysql.so > > With all extensions uncommented, session.so uncommented, mysql.so commented > out > no bus error. > > All extensions uncommented, mysql.so uncommented, session.so commented out > no bus error. > > All extensions commented out, mysql.so commented out, session.so uncommented > no bus error. > > All extensions commented out, session.so commented out, mysql.so uncommented > no bus error. > > All extensions commented out, session.so and mysql.so uncommented > bus error. > > thanks. > doug Hi Doug, What happens if you swap the order of session.so and mysql.so and try the same tests? From what I see on this page (http://forums.freebsd.org/archive/index.php/t-927.html), mysql.so should go before session.so. If that results in the same problems, that's when I start firing up the Apache process with truss to see what's called before the bus error. You can do that like so: truss -f -a -s 256 -o /tmp/apache.log /usr/local/sbin/httpd Then reproduce the bus error and stop the main Apache process. /tmp/apache.log may contain some clues about what the processes were doing before the crash, especially if you search for "php", "session" or "mysql" in the file. Regards, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/sourcehosting/ - Follow me, follow you -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFL2JoP0sRouByUApARAsHvAJ9TtCAYX3b5HYGNoIW1bAfEn+soiQCeMpkc D/rEGi03nhq2pkZWInhQfmo= =9y4B -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: apache signal bus error (10)
On Wed, Apr 28, 2010 at 3:44 PM, Greg Larkin wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > doug schmidt wrote: >> On Wed, Apr 28, 2010 at 1:44 PM, doug schmidt >> wrote: >>> On Wed, Apr 28, 2010 at 11:28 AM, doug schmidt >>> wrote: >>>> On Wed, Apr 28, 2010 at 10:23 AM, Greg Larkin wrote: >>>>> -BEGIN PGP SIGNED MESSAGE- >>>>> Hash: SHA1 >>>>> >>>>> doug schmidt wrote: >>>>>> On a 7.3-release box, I upgraded to php 5.3.2 + extensions. All seems >>>>>> [Tue Apr 27 16:08:37 2010] [notice] child pid 37609 exit signal Bus >>>>>> error (10) >>>>>> >>>>> Check out this page: >>>>> http://www.pingle.org/2007/09/22/php-crashes-extensions-workaround >>>> I'll give the script a try and see. If not, at least I know the >>>> specific extension >>>> and can test moving the order it is in. >>>> >>> I've tried using the script, then moving the session.so extension one >>> after the other. >>> Restarting apache each time and the same bus error. >>> >>> any other ideas? >>> >> I now have everything commented out in extensions.ini except for session.so >> There is no bus error, so I'll test moving the extensions order some >> more. Find it >> sooner or later. Real pain, that the order on one box, does not matter >> on another >> box. > Do you get a core file anywhere from the Apache process? It would be > interesting to get a backtrace so you can figure out what module is > causing the problem. Hi Greg, Unfortunately, no core files anywhere. The problem looks like session.so and mysql.so With all extensions uncommented, session.so uncommented, mysql.so commented out no bus error. All extensions uncommented, mysql.so uncommented, session.so commented out no bus error. All extensions commented out, mysql.so commented out, session.so uncommented no bus error. All extensions commented out, session.so commented out, mysql.so uncommented no bus error. All extensions commented out, session.so and mysql.so uncommented bus error. thanks. doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: apache signal bus error (10)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 doug schmidt wrote: > On Wed, Apr 28, 2010 at 1:44 PM, doug schmidt > wrote: >> On Wed, Apr 28, 2010 at 11:28 AM, doug schmidt >> wrote: >>> On Wed, Apr 28, 2010 at 10:23 AM, Greg Larkin wrote: >>>> -BEGIN PGP SIGNED MESSAGE- >>>> Hash: SHA1 >>>> >>>> doug schmidt wrote: >>>>> On a 7.3-release box, I upgraded to php 5.3.2 + extensions. All seems >>>>> [Tue Apr 27 16:08:37 2010] [notice] child pid 37609 exit signal Bus error >>>>> (10) >>>>> >>>> Check out this page: >>>> http://www.pingle.org/2007/09/22/php-crashes-extensions-workaround >>> I'll give the script a try and see. If not, at least I know the >>> specific extension >>> and can test moving the order it is in. >>> >> I've tried using the script, then moving the session.so extension one >> after the other. >> Restarting apache each time and the same bus error. >> >> any other ideas? >> > > I now have everything commented out in extensions.ini except for session.so > There is no bus error, so I'll test moving the extensions order some > more. Find it > sooner or later. Real pain, that the order on one box, does not matter > on another > box. > > doug Hi Doug, Do you get a core file anywhere from the Apache process? It would be interesting to get a backtrace so you can figure out what module is causing the problem. Regards, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/sourcehosting/ - Follow me, follow you -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFL2JAt0sRouByUApARAlDWAKCKSLANmabyTCV17lqXWc/Hiee6+gCfSwWX cxQf8/Y/OY2yHWVfp+bABks= =Dh6F -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: apache signal bus error (10)
On Wed, Apr 28, 2010 at 1:44 PM, doug schmidt wrote: > On Wed, Apr 28, 2010 at 11:28 AM, doug schmidt > wrote: >> On Wed, Apr 28, 2010 at 10:23 AM, Greg Larkin wrote: >>> -BEGIN PGP SIGNED MESSAGE- >>> Hash: SHA1 >>> >>> doug schmidt wrote: >>>> On a 7.3-release box, I upgraded to php 5.3.2 + extensions. All seems >> >>>> [Tue Apr 27 16:08:37 2010] [notice] child pid 37609 exit signal Bus error >>>> (10) >>>> >> >>> Check out this page: >>> http://www.pingle.org/2007/09/22/php-crashes-extensions-workaround >> >> I'll give the script a try and see. If not, at least I know the >> specific extension >> and can test moving the order it is in. >> > > I've tried using the script, then moving the session.so extension one > after the other. > Restarting apache each time and the same bus error. > > any other ideas? > I now have everything commented out in extensions.ini except for session.so There is no bus error, so I'll test moving the extensions order some more. Find it sooner or later. Real pain, that the order on one box, does not matter on another box. doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: apache signal bus error (10)
On Wed, Apr 28, 2010 at 11:28 AM, doug schmidt wrote: > On Wed, Apr 28, 2010 at 10:23 AM, Greg Larkin wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> doug schmidt wrote: >>> On a 7.3-release box, I upgraded to php 5.3.2 + extensions. All seems > >>> [Tue Apr 27 16:08:37 2010] [notice] child pid 37609 exit signal Bus error >>> (10) >>> > >> Check out this page: >> http://www.pingle.org/2007/09/22/php-crashes-extensions-workaround > > I'll give the script a try and see. If not, at least I know the > specific extension > and can test moving the order it is in. > I've tried using the script, then moving the session.so extension one after the other. Restarting apache each time and the same bus error. any other ideas? thanks. doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: apache signal bus error (10)
On Wed, Apr 28, 2010 at 10:23 AM, Greg Larkin wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > doug schmidt wrote: >> On a 7.3-release box, I upgraded to php 5.3.2 + extensions. All seems >> [Tue Apr 27 16:08:37 2010] [notice] child pid 37609 exit signal Bus error >> (10) >> > Check out this page: > http://www.pingle.org/2007/09/22/php-crashes-extensions-workaround Greg, I've seen this before when I was dealing with php cli dumping core. I did not think about this since I was not getting any core dumps. I'll give the script a try and see. If not, at least I know the specific extension and can test moving the order it is in. thanks. doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: apache signal bus error (10)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 doug schmidt wrote: > On a 7.3-release box, I upgraded to php 5.3.2 + extensions. All seems > to be working fine with our php developed application, > however when I start apache, I get this in the apache error log; > > [Tue Apr 27 16:08:33 2010] [notice] Apache/2.2.14 (FreeBSD) PHP/5.3.2 > with Suhosin-Patch mod_ssl/2.2.14 OpenSSL/1.0.0 DAV/2 configured -- > resuming normal operations > [Tue Apr 27 16:08:37 2010] [notice] child pid 37609 exit signal Bus error (10) > > This bus error only happens a few seconds after starting apache. In > trying to track this down, I find that the culprit is > "extension=session.so" in extensions.ini > If I comment this out, there is no bus error. > > Anything else I can do to try and resolve this? > > thanks. > doug Hi Doug, Check out this page: http://www.pingle.org/2007/09/22/php-crashes-extensions-workaround There's a link to a script (fixphpextorder.sh) that will re-order your extensions.ini file and hopefully fix the core dump problem you have. Hope that helps, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/sourcehosting/ - Follow me, follow you -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFL2ET30sRouByUApARAmI2AJ9zyAA28juefuM4zr8uVIkGhlBgMwCdGfRd TAEJY6tG2TIx6hBYqQCnlQI= =v7Fm -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
apache signal bus error (10)
On a 7.3-release box, I upgraded to php 5.3.2 + extensions. All seems to be working fine with our php developed application, however when I start apache, I get this in the apache error log; [Tue Apr 27 16:08:33 2010] [notice] Apache/2.2.14 (FreeBSD) PHP/5.3.2 with Suhosin-Patch mod_ssl/2.2.14 OpenSSL/1.0.0 DAV/2 configured -- resuming normal operations [Tue Apr 27 16:08:37 2010] [notice] child pid 37609 exit signal Bus error (10) This bus error only happens a few seconds after starting apache. In trying to track this down, I find that the culprit is "extension=session.so" in extensions.ini If I comment this out, there is no bus error. Anything else I can do to try and resolve this? thanks. doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: firefox3.6 dumps core - bus error
On Wed, Feb 10, 2010 at 02:27:26PM +, Anton Shterenlikht wrote: > On Tue, Feb 09, 2010 at 04:15:13PM +, Anton Shterenlikht wrote: > > On 9.0-current ia64, firefox-3.6,1: > > > > TZAV> firefox3 & > > [6] 91741 > > TZAV> Bus error (core dumped) > > > > [6]Exit 138 firefox3 > > TZAV> gdb /usr/local/bin/firefox3 ./firefox-bin.core > > GNU gdb 6.1.1 [FreeBSD] > > Copyright 2004 Free Software Foundation, Inc. > > GDB is free software, covered by the GNU General Public License, and you are > > welcome to change it and/or distribute copies of it under certain > > conditions. > > Type "show copying" to see the conditions. > > There is absolutely no warranty for GDB. Type "show warranty" for details. > > This GDB was configured as > > "ia64-marcel-freebsd"..."/usr/local/bin/firefox3": not in executable > > format: File format not recognized > > > > Core was generated by `firefox-bin'. > > Program terminated with signal 10, Bus error. > > #0 0x200041082fe0 in ?? () > > (gdb) bt > > #0 0x200041082fe0 in ?? () > > #1 0x2000412e20c0 in ?? () > > Previous frame identical to this frame (corrupt stack?) > > (gdb) > > I've rebuilt firefox with debugging support, so > now I get tons of console output culminating in > someting like this: > > ++DOCSHELL 0x200049046800 == 8 > ++DOMWINDOW == 14 (0x20004b6bbc58) [serial = 18] [outer = 0x0] > WARNING: Positioned frame that does not handle positioned kids; looking > further up the parent chain: file nsCSSFrameConstructor.cpp, line 5724 > WARNING: Positioned frame that does not handle positioned kids; looking > further up the parent chain: file nsCSSFrameConstructor.cpp, line 5724 > ++DOMWINDOW == 15 (0x20004b768058) [serial = 19] [outer = > 0x20004b6bbc00] > WARNING: NS_ENSURE_TRUE(aURI) failed: file nsDefaultURIFixup.cpp, line 76 > ++DOMWINDOW == 16 (0x20004b6b9458) [serial = 20] [outer = > 0x20004b6bbc00] > WARNING: Positioned frame that does not handle positioned kids; looking > further up the parent chain: file nsCSSFrameConstructor.cpp, line 5724 > WARNING: Positioned frame that does not handle positioned kids; looking > further up the parent chain: file nsCSSFrameConstructor.cpp, line 5724 > --DOMWINDOW == 15 (0x20004b768458) [serial = 17] [outer = > 0x20004ae77c00] [url = http://www.monkey.org/~provos/crawl/] > --DOCSHELL 0x20004b473000 == 7 > --DOMWINDOW == 14 (0x20004ae77c58) [serial = 15] [outer = 0x0] [url = > http://www.monkey.org/~provos/crawl/] > --DOCSHELL 0x200049046800 == 6 > --DOMWINDOW == 13 (0x20004b768058) [serial = 19] [outer = > 0x20004b6bbc00] [url = about:blank] > --DOMWINDOW == 12 (0x20004b6b9458) [serial = 20] [outer = > 0x20004b6bbc00] [url = http://larbin.sourceforge.net/] > --DOMWINDOW == 11 (0x20004b6bbc58) [serial = 18] [outer = 0x0] [url = > http://larbin.sourceforge.net/] > ++DOMWINDOW == 12 (0x20004a718058) [serial = 21] [outer = > 0x20004a71a800] > ###!!! ASSERTION: XPConnect is being called on a scope without a 'Components' > property!: 'Error', file xpcwrappednativescope.cpp, line 786 > ###!!! ASSERTION: XPConnect is being called on a scope without a 'Components' > property!: 'Error', file xpcwrappednativescope.cpp, line 786 > ###!!! ASSERTION: XPConnect is being called on a scope without a 'Components' > property!: 'Error', file xpcwrappednativescope.cpp, line 786 > ###!!! ASSERTION: XPConnect is being called on a scope without a 'Components' > property!: 'Error', file xpcwrappednativescope.cpp, line 786 > *** e = [Exception... "Component returned failure code: 0x80570016 > (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]" nsresult: > "0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE)" location: "JS frame :: > chrome://browser/content/utilityOverlay.js :: getShellService :: line 326" > data: no] > WARNING: Positioned frame that does not handle positioned kids; looking > further up the parent chain: file nsCSSFrameConstructor.cpp, line 5724 > ++DOCSHELL 0x20004b6afc00 == 7 > ++DOMWINDOW == 13 (0x20004b7c5058) [serial = 22] [outer = 0x0] > WARNING: Positioned frame that does not handle positioned kids; looking > further up the parent chain: file nsCSSFrameConstructor.cpp, line 5724 > WARNING: Positioned frame that does not handle positioned kids; looking > further up the parent chain: file nsCSSFrameConstructor.cpp, line 5724 > ++DOMWINDOW == 14 (0x20004b7c4458) [serial =
Re: firefox3.6 dumps core - bus error
On Tue, Feb 09, 2010 at 04:15:13PM +, Anton Shterenlikht wrote: > On 9.0-current ia64, firefox-3.6,1: > > TZAV> firefox3 & > [6] 91741 > TZAV> Bus error (core dumped) > > [6]Exit 138 firefox3 > TZAV> gdb /usr/local/bin/firefox3 ./firefox-bin.core > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "ia64-marcel-freebsd"..."/usr/local/bin/firefox3": > not in executable format: File format not recognized > > Core was generated by `firefox-bin'. > Program terminated with signal 10, Bus error. > #0 0x200041082fe0 in ?? () > (gdb) bt > #0 0x200041082fe0 in ?? () > #1 0x2000412e20c0 in ?? () > Previous frame identical to this frame (corrupt stack?) > (gdb) I've rebuilt firefox with debugging support, so now I get tons of console output culminating in someting like this: ++DOCSHELL 0x200049046800 == 8 ++DOMWINDOW == 14 (0x20004b6bbc58) [serial = 18] [outer = 0x0] WARNING: Positioned frame that does not handle positioned kids; looking further up the parent chain: file nsCSSFrameConstructor.cpp, line 5724 WARNING: Positioned frame that does not handle positioned kids; looking further up the parent chain: file nsCSSFrameConstructor.cpp, line 5724 ++DOMWINDOW == 15 (0x20004b768058) [serial = 19] [outer = 0x20004b6bbc00] WARNING: NS_ENSURE_TRUE(aURI) failed: file nsDefaultURIFixup.cpp, line 76 ++DOMWINDOW == 16 (0x20004b6b9458) [serial = 20] [outer = 0x20004b6bbc00] WARNING: Positioned frame that does not handle positioned kids; looking further up the parent chain: file nsCSSFrameConstructor.cpp, line 5724 WARNING: Positioned frame that does not handle positioned kids; looking further up the parent chain: file nsCSSFrameConstructor.cpp, line 5724 --DOMWINDOW == 15 (0x20004b768458) [serial = 17] [outer = 0x20004ae77c00] [url = http://www.monkey.org/~provos/crawl/] --DOCSHELL 0x20004b473000 == 7 --DOMWINDOW == 14 (0x20004ae77c58) [serial = 15] [outer = 0x0] [url = http://www.monkey.org/~provos/crawl/] --DOCSHELL 0x200049046800 == 6 --DOMWINDOW == 13 (0x20004b768058) [serial = 19] [outer = 0x20004b6bbc00] [url = about:blank] --DOMWINDOW == 12 (0x20004b6b9458) [serial = 20] [outer = 0x20004b6bbc00] [url = http://larbin.sourceforge.net/] --DOMWINDOW == 11 (0x20004b6bbc58) [serial = 18] [outer = 0x0] [url = http://larbin.sourceforge.net/] ++DOMWINDOW == 12 (0x20004a718058) [serial = 21] [outer = 0x20004a71a800] ###!!! ASSERTION: XPConnect is being called on a scope without a 'Components' property!: 'Error', file xpcwrappednativescope.cpp, line 786 ###!!! ASSERTION: XPConnect is being called on a scope without a 'Components' property!: 'Error', file xpcwrappednativescope.cpp, line 786 ###!!! ASSERTION: XPConnect is being called on a scope without a 'Components' property!: 'Error', file xpcwrappednativescope.cpp, line 786 ###!!! ASSERTION: XPConnect is being called on a scope without a 'Components' property!: 'Error', file xpcwrappednativescope.cpp, line 786 *** e = [Exception... "Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]" nsresult: "0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE)" location: "JS frame :: chrome://browser/content/utilityOverlay.js :: getShellService :: line 326" data: no] WARNING: Positioned frame that does not handle positioned kids; looking further up the parent chain: file nsCSSFrameConstructor.cpp, line 5724 ++DOCSHELL 0x20004b6afc00 == 7 ++DOMWINDOW == 13 (0x20004b7c5058) [serial = 22] [outer = 0x0] WARNING: Positioned frame that does not handle positioned kids; looking further up the parent chain: file nsCSSFrameConstructor.cpp, line 5724 WARNING: Positioned frame that does not handle positioned kids; looking further up the parent chain: file nsCSSFrameConstructor.cpp, line 5724 ++DOMWINDOW == 14 (0x20004b7c4458) [serial = 23] [outer = 0x20004b7c5000] WARNING: Positioned frame that does not handle positioned kids; looking further up the parent chain: file nsCSSFrameConstructor.cpp, line 5724 ++DOMWINDOW == 15 (0x20004b7c2858) [serial = 24] [outer = 0x20004b7c5000] *** e = [Exception... "Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]" nsresult: "0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE)" location: "JS frame :: ch
Re: firefox3.6 dumps core - bus error
On Tue, Feb 09, 2010 at 04:55:09PM -0300, Jorge Medina wrote: > On Tue, Feb 9, 2010 at 1:15 PM, Anton Shterenlikht > wrote: > > On 9.0-current ia64, firefox-3.6,1: > > > > TZAV> firefox3 & > > [6] 91741 > > TZAV> Bus error (core dumped) > > > > [6] Exit 138 firefox3 > > TZAV> gdb /usr/local/bin/firefox3 ./firefox-bin.core > > GNU gdb 6.1.1 [FreeBSD] > > Copyright 2004 Free Software Foundation, Inc. > > GDB is free software, covered by the GNU General Public License, and you are > > welcome to change it and/or distribute copies of it under certain > > conditions. > > Type "show copying" to see the conditions. > > There is absolutely no warranty for GDB. Type "show warranty" for details. > > This GDB was configured as > > "ia64-marcel-freebsd"..."/usr/local/bin/firefox3": not in executable > > format: File format not recognized > > > > Core was generated by `firefox-bin'. > > Program terminated with signal 10, Bus error. > > #0 0x200041082fe0 in ?? () > > (gdb) bt > > #0 0x200041082fe0 in ?? () > > #1 0x2000412e20c0 in ?? () > > Previous frame identical to this frame (corrupt stack?) > > (gdb) > > > > > > Please advise > > anton > > > > echo sem_load="YES" > /boot/loader.conf > reboot I've options P1003_1B_SEMAPHORES in the kernel config file already. This is a dual cpu box with SMP kernel. It seems to crash only on "heavy" sites, e.g. jpost.com. I've seen some posts in the last couple of days where the problem was attributed to SMP. I can confirm that firefox3.6 runs fine on UP sparc64. many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: firefox3.6 dumps core - bus error
On Tue, Feb 9, 2010 at 1:15 PM, Anton Shterenlikht wrote: > On 9.0-current ia64, firefox-3.6,1: > > TZAV> firefox3 & > [6] 91741 > TZAV> Bus error (core dumped) > > [6] Exit 138 firefox3 > TZAV> gdb /usr/local/bin/firefox3 ./firefox-bin.core > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "ia64-marcel-freebsd"..."/usr/local/bin/firefox3": > not in executable format: File format not recognized > > Core was generated by `firefox-bin'. > Program terminated with signal 10, Bus error. > #0 0x200041082fe0 in ?? () > (gdb) bt > #0 0x200041082fe0 in ?? () > #1 0x2000412e20c0 in ?? () > Previous frame identical to this frame (corrupt stack?) > (gdb) > > > Please advise > anton > > -- > Anton Shterenlikht > Room 2.6, Queen's Building > Mech Eng Dept > Bristol University > University Walk, Bristol BS8 1TR, UK > Tel: +44 (0)117 331 5944 > Fax: +44 (0)117 929 4423 > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > echo sem_load="YES" > /boot/loader.conf reboot -- Jorge Andrés Medina Oliva. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
firefox3.6 dumps core - bus error
On 9.0-current ia64, firefox-3.6,1: TZAV> firefox3 & [6] 91741 TZAV> Bus error (core dumped) [6]Exit 138 firefox3 TZAV> gdb /usr/local/bin/firefox3 ./firefox-bin.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "ia64-marcel-freebsd"..."/usr/local/bin/firefox3": not in executable format: File format not recognized Core was generated by `firefox-bin'. Program terminated with signal 10, Bus error. #0 0x200041082fe0 in ?? () (gdb) bt #0 0x200041082fe0 in ?? () #1 0x2000412e20c0 in ?? () Previous frame identical to this frame (corrupt stack?) (gdb) Please advise anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: "Bus error: 10 (core dumped)" on FreeBSD 7.0
At 03:51 AM 3/16/2008, Vladimir Ch. wrote: After upgrading to FreeBSD 7.0 some of the programs stopped working: when trying to launch emacs or sbcl I am getting "Bus error: 10". Searching the internet revealed that this could be hardware problem - but 6.2, 6.3 ran the same box before without any errors. Windows XP also works on the same computer. I use GENERIC kernel. You need to rebuild your ports if you have not done so. You will need to also rebuild any libraries the ports depend on as well. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: "Bus error: 10 (core dumped)" on FreeBSD 7.0
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Vladimir Ch. > Sent: Sunday, March 16, 2008 12:51 AM > To: freebsd-questions@freebsd.org > Subject: "Bus error: 10 (core dumped)" on FreeBSD 7.0 > > > After upgrading to FreeBSD 7.0 some of the programs stopped working: when > trying to launch emacs or sbcl I am getting "Bus error: 10". > Searching the internet revealed that this could be hardware problem - but > 6.2, 6.3 ran the same box before without any errors. Windows XP also works > on the same computer. > I use GENERIC kernel. Did you recompile every program on your system after you upgraded to 7.0 or did you just assume that the 6.3 binaries would run unmodified? See: http://www.freebsd.org/releases/7.0R/announce.html "...Updating Existing Systems An upgrade of any existing system to FreeBSD 7.0-RELEASE constitutes a major version upgrade, so no matter which method you use to update an older system you should reinstall any ports you have installed on the machine. This will avoid binaries becoming linked to inconsistent sets of libraries when future port upgrades rebuild one port but not others that link to it. This can be done with: # portupgrade -faP after updating your system. Note some of the tools to help with this or the instructions below for FreeBSD Update are not installed by default (e.g. portupgrade, gpg, or similar tools like portmaster..." Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
"Bus error: 10 (core dumped)" on FreeBSD 7.0
After upgrading to FreeBSD 7.0 some of the programs stopped working: when trying to launch emacs or sbcl I am getting "Bus error: 10". Searching the internet revealed that this could be hardware problem - but 6.2, 6.3 ran the same box before without any errors. Windows XP also works on the same computer. I use GENERIC kernel. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bus error (core dumped)
Hello all i am tring to get apache13_modssl this on FreeeBSD ver 4.11 stable to work. apachectl start works ok but when i try to start apachectl startssl i get this on the command line tokyo.computerking.ca > /usr/local/etc/apache #apachectl startssl Bus error (core dumped) I get nothing in /var/log/apache/httpd-error.log or /var/log/apache/sl.computerking.ca.ssl-httpd-error.log which is my log for the first and only virtual ssl host. i get this in my /var/log/apache/ssl_engine_log [06/Nov/2006 14:28:13 76200] [info] Server: Apache/1.3.37, Interface: mod_ssl/2.8.28, Library: OpenSSL/0.9.8a [06/Nov/2006 14:28:13 76200] [info] Init: 1st startup round (still not detached) [06/Nov/2006 14:28:13 76200] [info] Init: Initializing OpenSSL library [06/Nov/2006 14:28:13 76200] [info] Init: Loading certificate & private key of SSL-aware server sl.computerking.ca:443:443 [06/Nov/2006 14:28:13 76200] [info] Init: Seeding PRNG with 136 bytes of entropy [06/Nov/2006 14:28:13 76200] [info] Init: Generating temporary RSA private keys (512/1024 bits) could this be that my self signed cert is 2048 bits it always seemed to work with apache2 please help. -- Computer King/CaNMail http://www.computerking.ca http://www.canmail.org Sales, Service, and Hosting Email, Data, and Web Packages Ask about web design specials Affiliates http://www.computerking.ca/pages/links/affiliates/affiliates.htm Maybe Computer Science should be in the College of Theology. -- R. S. Barton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
truss output of ssh Bus error (core dumped)
Thanks to member Lowell Gilbert I was able to run truss and generate output from my ssh Bus error (core dumped) problem. This only happens when I try to ssh out of the box as a normal user. I can ssh out as root. I"ve posted the file at http://www.jimarnold.org/truss.ssh.txt to see if anyone can decipher if for me. I am running 4.11-STABLE and openssh-3.6.1_5 The file ends with: getpid() = 32210 (0x7dd2) SIGNAL 10 SIGNAL 10 Process stopped because of: 16 process exit, rval = 138 Thanks, Jim ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ps "Bus error" under jail
Hi, The machine is running FreeBSD 6.0-RELEASE and i am trying out jails on it I have followed the tutorial in jail's man page and everythings seems working fine, except the ps command. When I execute ps, it say "Bus error" Here is the gdb output: GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd"...(no debugging symbols found)... Core was generated by `ps'. Program terminated with signal 10, Bus error. Reading symbols from /lib/libm.so.4...(no debugging symbols found)...done. Loaded symbols for /lib/libm.so.4 Reading symbols from /lib/libkvm.so.3...(no debugging symbols found)...done. Loaded symbols for /lib/libkvm.so.3 Reading symbols from /lib/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x28092398 in _kvm_initvtop () from /lib/libkvm.so.3 (gdb) backtrace #0 0x28092398 in _kvm_initvtop () from /lib/libkvm.so.3 Cannot access memory at address 0xbfbfdc6c Thanks Edwin ___ 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 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 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
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 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]"
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 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
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
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
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, 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, 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
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 & 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
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 & 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]"
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
Antwort: Re: bus error on build/ portupgrade is doing nothing
Hi, >>bus error >>I receive the following output on each port i try to upgrade. >>So, i thought it could be a problem of RAM, after changing the RAM >twice, >>the problem ist still there, so what could be the problem? >> >>#portupgrade unzip >>---> Upgrading 'unzip-5.52_1' to 'unzip-5.52_2' (archivers/unzip) >>---> Building '/usr/ports/archivers/unzip' >>===> Cleaning for unzip-5.52_2 >>===> Extracting for unzip-5.52_2 >>=> Checksum OK for unzip552.tar.gz. >>===> Patching for unzip-5.52_2 >>===> Applying FreeBSD patches for unzip-5.52_2 >>===> Configuring for unzip-5.52_2 >>===> Building for unzip-5.52_2 >>NOTE: use bsd target for non-Intel FreeBSD compiles (if any). >>make unzips CC="cc" LD="cc" AS="cc" CF="-Wall -I. -DASM_CRC -DUNIX >-DBSD -O >>-pipe -DUSE_UNSHRINK" AF="-Di386 -O -pipe -DUSE_UNSHRINK" >CRC32=crc_gcc >>cc -c -Wall -I. -DASM_CRC -DUNIX -DBSD -O -pipe -DUSE_UNSHRINK >unzip.c >>unzip.c: In function `unzip': >>unzip.c:1032: internal compiler error: Bus error >>Please submit a full bug report, >>with preprocessed source if appropriate. >>See http://gcc.gnu.org/bugs.html> for instructions. >>*** Error code 1 > >Does it always die at the same place in the build? Typically when >I've seen "internal compiler error", bad hardware is the >culprit. Especially if the build dies at different places each time. It is always the same place where the build dies. Also, trying to build the world, stops with a compiler error. Ah, FreeBSD 5.4-RELEASE-p6. >>(2) portupgrade does not build >>Trying to update amavisd-new or apache with portupgrade does not >work. It >>just do nothing. >>So, other ports are working to update, others not. So what could be >the >>problem? > >If you run portupgrade with -v, does it give any more detail? Hard >to say what the problem might be without more details. Based on your >first question, it's very likely to be a symptom of the same problem. Uh, my fault. -v says that the port is up-to-date, but it is not. Maybe a problem with the "INDEX". I have this problem also on a machine which builds ports and world without any error, so i do not think it is based on the same problem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
bus error on build/ portupgrade is doing nothing
Hi, two questions: (1) bus error I receive the following output on each port i try to upgrade. So, i thought it could be a problem of RAM, after changing the RAM twice, the problem ist still there, so what could be the problem? #portupgrade unzip ---> Upgrading 'unzip-5.52_1' to 'unzip-5.52_2' (archivers/unzip) ---> Building '/usr/ports/archivers/unzip' ===> Cleaning for unzip-5.52_2 ===> Extracting for unzip-5.52_2 => Checksum OK for unzip552.tar.gz. ===> Patching for unzip-5.52_2 ===> Applying FreeBSD patches for unzip-5.52_2 ===> Configuring for unzip-5.52_2 ===> Building for unzip-5.52_2 NOTE: use bsd target for non-Intel FreeBSD compiles (if any). make unzips CC="cc" LD="cc" AS="cc" CF="-Wall -I. -DASM_CRC -DUNIX -DBSD -O -pipe -DUSE_UNSHRINK" AF="-Di386 -O -pipe -DUSE_UNSHRINK" CRC32=crc_gcc cc -c -Wall -I. -DASM_CRC -DUNIX -DBSD -O -pipe -DUSE_UNSHRINK unzip.c unzip.c: In function `unzip': unzip.c:1032: internal compiler error: Bus error Please submit a full bug report, with preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html> for instructions. *** Error code 1 (2) portupgrade does not build Trying to update amavisd-new or apache with portupgrade does not work. It just do nothing. So, other ports are working to update, others not. So what could be the problem? Thanks in advance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FW: Re: BUS ERROR from freecolor
hi I have Compaq Deskpro 4000, Processor Celeron 400MHz # sysctl hw hw.machine: i386 hw.model: Pentium II/Pentium II Xeon/Celeron hw.ncpu: 1 hw.byteorder: 1234 hw.physmem: 527929344 hw.usermem: 424464384 hw.pagesize: 4096 hw.floatingpoint: 1 hw.machine_arch: i386 hw.realmem: 536870912 hw.aac.iosize_max: 65536 hw.an.an_dump: off hw.an.an_cache_mode: dbm hw.an.an_cache_mcastonly: 0 hw.an.an_cache_iponly: 1 hw.ata.ata_dma: 1 hw.ata.wc: 1 hw.ata.atapi_dma: 0 hw.cardbus.debug: 0 hw.cardbus.cis_debug: 0 hw.cs.debug: 0 hw.cs.ignore_checksum_failure: 0 hw.cs.recv_delay: 570 hw.firewire.try_bmr: 1 hw.firewire.hold_count: 3 hw.firewire.fwmem.eui64_hi: 0 hw.firewire.fwmem.eui64_lo: 0 hw.firewire.fwmem.speed: 2 hw.firewire.fwe.stream_ch: 1 hw.firewire.fwe.tx_speed: 2 hw.firewire.fwe.rx_queue_len: 128 hw.firewire.sbp.auto_login: 1 hw.firewire.sbp.max_speed: -1 hw.firewire.sbp.exclusive_login: 1 hw.firewire.sbp.login_delay: 1000 hw.firewire.sbp.scan_delay: 500 hw.firewire.sbp.use_doorbell: 0 hw.firewire.sbp.tags: 0 hw.pccard.debug: 0 hw.pccard.cis_debug: 0 hw.cbb.start_memory: 2281701376 hw.cbb.start_16_io: 256 hw.cbb.start_32_io: 4096 hw.cbb.debug: 0 hw.pcic.intr_mask: 57016 hw.pci.enable_io_modes: 1 hw.pci.do_powerstate: 0 hw.pci.host_mem_start: 2147483648 hw.pci.irq_override_mask: 57080 hw.wi.txerate: 0 hw.wi.debug: 0 hw.xe.debug: 0 hw.intr_storm_threshold: 500 hw.availpages: 128889 hw.bus.devctl_disable: 0 hw.dc_quick: 1 hw.ste.rxsyncs: 0 hw.kbd.keymap_restrict_change: 0 hw.syscons.saver.keybonly: 1 hw.syscons.bell: 1 hw.syscons.sc_no_suspend_vtswitch: 0 hw.busdma.total_bpages: 33 hw.busdma.zone0.total_bpages: 1 hw.busdma.zone0.free_bpages: 1 hw.busdma.zone0.reserved_bpages: 0 hw.busdma.zone0.active_bpages: 0 hw.busdma.zone0.total_bounced: 0 hw.busdma.zone0.total_deferred: 0 hw.busdma.zone0.lowaddr: 0x hw.busdma.zone0.alignment: 4096 hw.busdma.zone0.boundary: 0 hw.busdma.zone1.total_bpages: 32 hw.busdma.zone1.free_bpages: 32 hw.busdma.zone1.reserved_bpages: 0 hw.busdma.zone1.active_bpages: 0 hw.busdma.zone1.total_bounced: 0 hw.busdma.zone1.total_deferred: 0 hw.busdma.zone1.lowaddr: 0x hw.busdma.zone1.alignment: 2 hw.busdma.zone1.boundary: 65536 hw.clockrate: 399 hw.instruction_sse: 0 hw.em0.debug_info: -1 hw.em0.stats: -1 hw.em0.rx_int_delay: 0 hw.em0.tx_int_delay: 66 hw.em0.rx_abs_int_delay: 66 hw.em0.tx_abs_int_delay: 66 greetings piotr ___ Join Excite! - http://www.excite.com The most personalized portal on the Web! --- Begin Message --- On Thu, 2005-07-14 at 16:26 +0200, Simon Barner wrote: > PK wrote: > > I have freeBSD 5.4 and newest ports tree update. > > I've installed freecolor from ports without errors, > > but if I try to start it, I get following error: > > Works fine here. > > Please report this to freecolor's maintainer (see the Makefile). This > might be a 64bit issue, so tell him what platform you are seeing this > error on. He already has :) It works for me also, and I even gave him a pre-compiled package that was known to work on my system. I hadn't thought about the 64 bit issue - PK, what platform are you running this on? That said - it works on my sparc64... Cheers, Tim. -- Tim Bishop http://www.bishnet.net/tim/ PGP Key: 0x5AE7D984 --- End Message --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
freecolor won't start because of BUS ERROR
hi I have a fresh installation of freeBSD 5.4 and did ports tree update. I've installed freecolor from ports, but won't start: # /usr/local/bin/freecolor -o Bus error ___ Join Excite! - http://www.excite.com The most personalized portal on the Web! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bus error w/ mozilla or firefox
On Mon, Apr 11, 2005 at 01:11:14AM +0200, Bachelier Vincent wrote: > Does it segment fault when you start it from console ? > If it does, just delete .gtk*, it should work after that. It wasn't a segv, it was a "Bus error (core dumped)". This was left in ~/. -rw--- 1 kline kline 3612672 Apr 10 17:50 mozilla-bin.core I believe that the update script will run to completion once I have ruby18 updated. But it dies on me too... :-( gary > > Le Dimanche 10 Avril 2005 21:36, Gary Kline a écrit : > > People, > > > > I need some clues as to *why* after the gnome update script > > has finished on my laptop neither mozilla nor firefox run. > > > > Note that on my laptop, there were not many files that > > needed to be rebuilt. > > > > One question seems apropos here: why can't the gnome > > (and kde) upgrades be handled thru Packages rather than > > by source rebuilding? > > > > (AFter 2+ days of running the script here on "tao" > > --a 750MHz platform--I the script may have succeeded; > > the laptop in a 400MHz ThinkPad. ... ) > > > > Help? Suggestions anybody? > > > > gary > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Gary Kline [EMAIL PROTECTED] www.thought.org Public service Unix ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bus error w/ mozilla or firefox
Does it segment fault when you start it from console ? If it does, just delete .gtk*, it should work after that. Le Dimanche 10 Avril 2005 21:36, Gary Kline a écrit : > People, > > I need some clues as to *why* after the gnome update script > has finished on my laptop neither mozilla nor firefox run. > > Note that on my laptop, there were not many files that > needed to be rebuilt. > > One question seems apropos here: why can't the gnome > (and kde) upgrades be handled thru Packages rather than > by source rebuilding? > > (AFter 2+ days of running the script here on "tao" > --a 750MHz platform--I the script may have succeeded; > the laptop in a 400MHz ThinkPad. ... ) > > Help? Suggestions anybody? > > gary ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
bus error w/ mozilla or firefox
People, I need some clues as to *why* after the gnome update script has finished on my laptop neither mozilla nor firefox run. Note that on my laptop, there were not many files that needed to be rebuilt. One question seems apropos here: why can't the gnome (and kde) upgrades be handled thru Packages rather than by source rebuilding? (AFter 2+ days of running the script here on "tao" --a 750MHz platform--I the script may have succeeded; the laptop in a 400MHz ThinkPad. ... ) Help? Suggestions anybody? gary -- Gary Kline [EMAIL PROTECTED] www.thought.org Public service Unix ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PHP / Apache bus error
Peter Risdon helpful contributes: You don't _have_ to boot into single user mode. See below. Okay, cool. I did it. Upgraded to 4.11 without any problems. However ... I still have the following problems: 1. child pid 28305 exit signal Segmentation fault (11) messages (lots of 'em) in httpd error logs. 2. Gallery doesn't work. Returns an empty page, and I get a Signal 10 in the error log. 3. Drupal doesn't work. Blank php page is returned. I'm fairly confident this is php / mysql / httpd related. So, for your reference, I have: apache+mod_ssl-1.3.33+2.8.22 php4-4.3.10_2 php4-gettext-4.3.10_2 php4-mysql-4.3.10_2 php4-pcre-4.3.10_2 php4-pear-4.3.10_2 php4-pgsql-4.3.10_2 php4-session-4.3.10_2 php4-xml-4.3.10_2 mysql-client-3.23.58 mysql-client-4.0.15 mysql-server-3.23.58 php4-mysql-4.3.10_2 zope-zmysqlda-2.0.8_1 I do not know HOW I ended up with two installs of mysql client .. but there ya go. So if anyone sees anything obvious in those versions ... I would love to hear about it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PHP / Apache bus error
On Wed, 2005-03-23 at 09:49 -0700, Tom Vilot wrote: > Peter Risdon helpful contributes: [...] > > On the 4.9 server, what should my supfile's tag be? > > *default release=cvs tag=RELENG_4_11 If you like. I'd use *default release=cvs tag=RELENG_4 The difference has been discussed exhaustively on this list before. This is a good example: http://lists.freebsd.org/pipermail/freebsd-questions/2004-July/053176.html > > Is that right? > > And I assume I would then be safe doing: > > rm -fr /usr/src No need for this line. If you've ever made world or kernel before there's a BIG need for: # cd /usr/obj # chflags -R noschg * # rm -rf * before doing it again. But this is all in the handbook. > cvsup stable-supfile #cvsup -g -L 2 stable-supfile Peter. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PHP / Apache bus error
Peter Risdon helpful contributes: > You don't _have_ to boot into single user mode. See below. Okay, cool. I have one last question (me thinks) before I attempt this. (and I'll attempt it on my home server, first, even though it is a 5.3 box. At least I can get practice). On the 4.9 server, what should my supfile's tag be? *default release=cvs tag=RELENG_4_11 Is that right? And I assume I would then be safe doing: rm -fr /usr/src cvsup stable-supfile [ re: going from 4.x to 5.x] > No, this would have some issues that you might be better avoiding > right now. I've since gathered that is the case. I can see it is possible, but since the server has two drives, I think I'll wait on this, install 5.3 on the second drive, and deal with that stuff then. > The only time I have ever had a problem with a remote upgrade within the > 4.x tree was when _I_ made a mistake. You think you're special, eh? :c) I make some JUICY mistakes sometimes, too!! > The only difference from the procedure in the handbook for a remote > upgrade is that you would not boot into single user mode at any point, > obviously, but instead do a normal reboot. Generally, I am the only user logged into the machine. So the only issue is running processes, which I am not all that worried about since right after the install I'm going to reboot. > Do read /usr/src/UPDATING, consider what you might need > in /etc/make.conf and understand how mergemaster(8) works before > Starting. Thank you, Peter. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PHP / Apache bus error
On Tue, 2005-03-22 at 19:31 -0700, Tom Vilot wrote: > Peter Risdon wrote: > > >>Can you explain why? What is it about 4.11 vs 4.9 with regard to this issue? > >> > >> > > > >Just that it's an up-to-date release. > > > >PHP and its extensions do depend on bits of the base system. You are > >using the very latest ported version, so far as I can see, with an out > >of date world. > > > > Okay, I suspect I'm going to have to bite the bullet. I must admit, tho, > I have some irrational fears about upgrading the core system. > > 1. I've never done it before > > 2. The server in question is in Texas. I am in Colorado. > > 3. I would rather not have to rent KVM and reboot into single user mode > ... but will if I must ... You don't _have_ to boot into single user mode. See below. > > (( sigh )) > > If I'm going to upgrade the system, does it make sense to just go > straight to 5.3? No, this would have some issues that you might be better avoiding right now. Going to 4.11 should be straightforward. Moving from 4.x to 5.3 is pretty complicated and a backup/reinstall is a better idea, so you can take full advantage of changes to the filesystem. The only time I have ever had a problem with a remote upgrade within the 4.x tree was when _I_ made a mistake. If you follow the handbook carefully, it should be fine. The procedure ensures you will have successfully completed the compilation of the base system (world) and kernel before either is installed. The only difference from the procedure in the handbook for a remote upgrade is that you would not boot into single user mode at any point, obviously, but instead do a normal reboot. Do read /usr/src/UPDATING, consider what you might need in /etc/make.conf and understand how mergemaster(8) works before starting. Peter. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PHP / Apache bus error
Peter Risdon wrote: Can you explain why? What is it about 4.11 vs 4.9 with regard to this issue? Just that it's an up-to-date release. PHP and its extensions do depend on bits of the base system. You are using the very latest ported version, so far as I can see, with an out of date world. Okay, I suspect I'm going to have to bite the bullet. I must admit, tho, I have some irrational fears about upgrading the core system. 1. I've never done it before 2. The server in question is in Texas. I am in Colorado. 3. I would rather not have to rent KVM and reboot into single user mode ... but will if I must ... (( sigh )) If I'm going to upgrade the system, does it make sense to just go straight to 5.3? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PHP / Apache bus error
On Tue, 2005-03-22 at 10:02 -0700, Tom Vilot wrote: > > But then, I've found most apache/php errors actually derive from some > > php extension and this can be traced by a process of elimination. It's > > often then a dependency of the extension that has been updated, or > > something. > > I'm starting to think there's something funky about PHP and MySQL. > > > > Is this something that will clear up if I move to FreeBSD 5.3? Or is > > > there some other known work-around? I ask because I have a 5.3 box here > > > at home that does not seem to be exhibiting this behavior. > > > Yes, but going to 4.11 should fix it as well. > > Can you explain why? What is it about 4.11 vs 4.9 with regard to this issue? Just that it's an up-to-date release. PHP and its extensions do depend on bits of the base system. You are using the very latest ported version, so far as I can see, with an out of date world. http://www.freebsd.org/ports/index.html says: The Ports Collection supports the latest release on the FreeBSD-CURRENT and FreeBSD-STABLE branches. Older releases are not supported and may or may not work correctly with an up-to-date ports collection. Over time, changes to the ports collection may rely on features that are not present in older releases. Wherever convenient, we try not to gratuitously break support for recent releases, but it is sometimes unavoidable. When this occurs, patches contributed by the user community to maintain support for older releases will usually be committed. Peter. Peter. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PHP / Apache bus error
> But then, I've found most apache/php errors actually derive from some > php extension and this can be traced by a process of elimination. It's > often then a dependency of the extension that has been updated, or > something. I'm starting to think there's something funky about PHP and MySQL. > > Is this something that will clear up if I move to FreeBSD 5.3? Or is > > there some other known work-around? I ask because I have a 5.3 box here > > at home that does not seem to be exhibiting this behavior. > Yes, but going to 4.11 should fix it as well. Can you explain why? What is it about 4.11 vs 4.9 with regard to this issue? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PHP / Apache bus error
On Tue, 2005-03-22 at 09:22 -0700, Tom Vilot wrote: > I've done a lot of snooping around Google to figure this out. I've come > to the conclusion that PHP just plain sucks ;c) > > I am fairly consistently getting bus errors in Apache when I use PHP (or > at least, I'm fairly sure it is due to PHP). One way to find out is to comment out the LoadModule php4_modulelibexec/apache/libphp4.so and AddModule mod_php4.c in httpd.conf and restart apache. I think you need to make sure this is the source of the problem before getting too involved in trying to fix it. But then, I've found most apache/php errors actually derive from some php extension and this can be traced by a process of elimination. It's often then a dependency of the extension that has been updated, or something. > Entries like: > > ... [notice] child pid 70121 exit signal Segmentation fault (11) > > Or if I run Apache in stand-alone mode, I will often simply get: > > Bus Error > > and it exits immediately. > > I am running php4-4.3.10_2 and apache+mod_ssl-1.3.33+2.8.22 on > FreeBSD 4.9 RELEASE (Generic kernel). > > Is this something that will clear up if I move to FreeBSD 5.3? Or is > there some other known work-around? I ask because I have a 5.3 box here > at home that does not seem to be exhibiting this behavior. Yes, but going to 4.11 should fix it as well. Peter. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
PHP / Apache bus error
I've done a lot of snooping around Google to figure this out. I've come to the conclusion that PHP just plain sucks ;c) I am fairly consistently getting bus errors in Apache when I use PHP (or at least, I'm fairly sure it is due to PHP). Entries like: ... [notice] child pid 70121 exit signal Segmentation fault (11) Or if I run Apache in stand-alone mode, I will often simply get: Bus Error and it exits immediately. I am running php4-4.3.10_2 and apache+mod_ssl-1.3.33+2.8.22 on FreeBSD 4.9 RELEASE (Generic kernel). Is this something that will clear up if I move to FreeBSD 5.3? Or is there some other known work-around? I ask because I have a 5.3 box here at home that does not seem to be exhibiting this behavior. Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xine bus error
Gert Cuykens wrote: On Sun, 6 Feb 2005 20:01:13 -0600, Donald J. O'Neill <[EMAIL PROTECTED]> wrote: On Sunday 06 February 2005 07:41 pm, Gert Cuykens wrote: On Mon, 07 Feb 2005 02:37:05 +0100, albi <[EMAIL PROTECTED]> wrote: Gert Cuykens wrote: you could try : cd /usr/ports/multimedia/mplayer-skins make NO_CHECKSUM=yes install and then compile mplayer itself Will the no check sum only be applied to the skin port only ? yes PS why does the maintainer not fix the port ? no idea, life is short, time is not cheap etc. Why do they call it NO_CHECKSUM ? whats wrong with CHECKSUM yes no ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Gert, The best way of doing this is to use "rm -r /usr/ports/distfiles/mplayer", then install mplayer-skins, or portupgrade, or whatever you decide to use; this allows you to download fresh versions of the skins with the correct file size and the correct MD5 checksum. Don PS Your now getting off topic from your original post. -- Donald J. O'Neill [EMAIL PROTECTED] I'm not totally useless, I can be used as a bad example. i deleted the distfiles but i still have no mplayer skins Yup, same here. mplayer-skins has been broken for a while now. I had the same problem last time I tried updating kmplayer. This is the same problem as PR 75943, which was submitted and closed on Jan 8, 2005. Either it wasn't actually fixed, or the distfiles on the remote sites have changed. I submitted a PR, ports/77192. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xine bus error
On Sun, 6 Feb 2005 20:01:13 -0600, Donald J. O'Neill <[EMAIL PROTECTED]> wrote: > On Sunday 06 February 2005 07:41 pm, Gert Cuykens wrote: > > On Mon, 07 Feb 2005 02:37:05 +0100, albi <[EMAIL PROTECTED]> wrote: > > > Gert Cuykens wrote: > > > >>you could try : > > > >>cd /usr/ports/multimedia/mplayer-skins > > > >>make NO_CHECKSUM=yes install > > > >> > > > >>and then compile mplayer itself > > > > > > > > Will the no check sum only be applied to the skin port only ? > > > > > > yes > > > > > > > PS why does the maintainer not fix the port ? > > > > > > no idea, > > > > > > life is short, time is not cheap etc. > > > > Why do they call it NO_CHECKSUM ? whats wrong with CHECKSUM yes no ? > > ___ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to > > "[EMAIL PROTECTED]" > Gert, > > The best way of doing this is to use "rm > -r /usr/ports/distfiles/mplayer", then install mplayer-skins, or > portupgrade, or whatever you decide to use; this allows you to download > fresh versions of the skins with the correct file size and the correct > MD5 checksum. > > Don > > PS Your now getting off topic from your original post. > -- > Donald J. O'Neill > [EMAIL PROTECTED] > > I'm not totally useless, > I can be used as a bad example. > i deleted the distfiles but i still have no mplayer skins ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xine bus error
On Sunday 06 February 2005 07:41 pm, Gert Cuykens wrote: > On Mon, 07 Feb 2005 02:37:05 +0100, albi <[EMAIL PROTECTED]> wrote: > > Gert Cuykens wrote: > > >>you could try : > > >>cd /usr/ports/multimedia/mplayer-skins > > >>make NO_CHECKSUM=yes install > > >> > > >>and then compile mplayer itself > > > > > > Will the no check sum only be applied to the skin port only ? > > > > yes > > > > > PS why does the maintainer not fix the port ? > > > > no idea, > > > > life is short, time is not cheap etc. > > Why do they call it NO_CHECKSUM ? whats wrong with CHECKSUM yes no ? > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" Gert, The best way of doing this is to use "rm -r /usr/ports/distfiles/mplayer", then install mplayer-skins, or portupgrade, or whatever you decide to use; this allows you to download fresh versions of the skins with the correct file size and the correct MD5 checksum. Don PS Your now getting off topic from your original post. -- Donald J. O'Neill [EMAIL PROTECTED] I'm not totally useless, I can be used as a bad example. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xine bus error
On Mon, 07 Feb 2005 02:37:05 +0100, albi <[EMAIL PROTECTED]> wrote: > >>you could try : > >>cd /usr/ports/multimedia/mplayer-skins > >>make NO_CHECKSUM=yes install > >> > >>and then compile mplayer itself I# make NO_CHECKSUM=yes ===> Vulnerability check disabled, database not found ===> Found saved configuration for mplayer-skins-1.1.1 => Abyss-1.1.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/mplayer. => Attempting to fetch from http://www.mplayerhq.hu/MPlayer/Skin/. fetch: http://www.mplayerhq.hu/MPlayer/Skin/Abyss-1.1.tar.bz2: size mismatch: expected 314296, actual 314302 => Attempting to fetch from http://ftp.lug.udel.edu/MPlayer/Skin/. fetch: http://ftp.lug.udel.edu/MPlayer/Skin/Abyss-1.1.tar.bz2: size mismatch: expected 314296, actual 314302 => Attempting to fetch from ftp://ftp.mplayerhq.hu/MPlayer/Skin/. fetch: ftp://ftp.mplayerhq.hu/MPlayer/Skin/Abyss-1.1.tar.bz2: size mismatch: expected 314296, actual 314302 => Attempting to fetch from ftp://ftp.lug.udel.edu/MPlayer/Skin/. fetch: ftp://ftp.lug.udel.edu/MPlayer/Skin/Abyss-1.1.tar.bz2: size mismatch: expected 314296, actual 314302 => Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/mplayer/. fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/mplayer/Abyss-1.1.tar.bz2: size mismatch: expected 314296, actual 314264 => Couldn't fetch it - please try to retrieve this => port manually into /usr/ports/distfiles/mplayer and try again. *** Error code 1 Stop in /usr/ports/multimedia/mplayer-skins. I# not wroking ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xine bus error
On Mon, 07 Feb 2005 02:37:05 +0100, albi <[EMAIL PROTECTED]> wrote: > Gert Cuykens wrote: > > >>you could try : > >>cd /usr/ports/multimedia/mplayer-skins > >>make NO_CHECKSUM=yes install > >> > >>and then compile mplayer itself > >> > > > > > > Will the no check sum only be applied to the skin port only ? > > yes > > > > > PS why does the maintainer not fix the port ? > > no idea, > > life is short, time is not cheap etc. > Why do they call it NO_CHECKSUM ? whats wrong with CHECKSUM yes no ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xine bus error
Gert Cuykens wrote: you could try : cd /usr/ports/multimedia/mplayer-skins make NO_CHECKSUM=yes install and then compile mplayer itself Will the no check sum only be applied to the skin port only ? yes PS why does the maintainer not fix the port ? no idea, life is short, time is not cheap etc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xine bus error
On Mon, 07 Feb 2005 02:30:14 +0100, albi <[EMAIL PROTECTED]> wrote: > Gert Cuykens wrote: > > > How do you install mplayer without skins ? > > you could try : > cd /usr/ports/multimedia/mplayer-skins > make NO_CHECKSUM=yes install > > and then compile mplayer itself > Will the no check sum only be applied to the skin port only ? PS why does the maintainer not fix the port ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xine bus error
Gert Cuykens wrote: How do you install mplayer without skins ? you could try : cd /usr/ports/multimedia/mplayer-skins make NO_CHECKSUM=yes install and then compile mplayer itself ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xine bus error
On Mon, 07 Feb 2005 01:03:47 +0100, albi <[EMAIL PROTECTED]> wrote: > Gert Cuykens wrote: > > > playing mp3's with xmms works perfect but when i open the same mp3 in > > xine i get this ? > > > > why would you want to mp3s with xine ? mplayer is imho the better > video-player for playing (streaming) mp3 and ogg anyway > > > I# xine > > This is xine (X11 gui) - a free video player v0.99.3. > > (c) 2000-2004 The xine Team. > > Bus error > > i suggest you install also mplayer, mpg321 and beep-media-player for > both mp3, ogg and mpeg, avi, wmv and mov files (i like choice ;^) > How do you install mplayer without skins ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xine bus error
Gert Cuykens wrote: playing mp3's with xmms works perfect but when i open the same mp3 in xine i get this ? why would you want to mp3s with xine ? mplayer is imho the better video-player for playing (streaming) mp3 and ogg anyway I# xine This is xine (X11 gui) - a free video player v0.99.3. (c) 2000-2004 The xine Team. Bus error i suggest you install also mplayer, mpg321 and beep-media-player for both mp3, ogg and mpeg, avi, wmv and mov files (i like choice ;^) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
xine bus error
playing mp3's with xmms works perfect but when i open the same mp3 in xine i get this ? I# xine This is xine (X11 gui) - a free video player v0.99.3. (c) 2000-2004 The xine Team. Bus error I# ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Firefox bus error
On Wed, 29 Dec 2004 10:57, Ian Moore wrote: > Hi, > I've just finished upgrading my ports after a cvsup a few days ago. Now > when I try to start firefox, all I get is > % firefox& > bus error > > I did some googling & found this: > > i solved the problem i told you about switching CFLAGS from -O2 -pipe > > -fomit-frame-pointer to a more "standard" -O -pipe > > > bye > > > > Eugenio > > eugenio.modesti at poste.it > > Unfortunately that doesn't help, since my CFLAGS is set to -O -pipe anyway. > I also tried renaming .mozilla so it could start from scratch, but that > just gave the following: > % firefox& > LoadPlugin: failed to initialize shared > library /usr/local/Acrobat5/Browsers/intellinux/nppdf.so > [/usr/local/Acrobat5/Browsers/intellinux/nppdf.so: Undefined symbol > "XtStrings"] > firefox-bin: Fatal IO error 78 (Function not implemented) on X server :0.0. > > Does anyone have any suggestions? > > Cheers, I fixed this by installing the latest update of the firefox port (firefox-1.0_6,1). Works quite nicely now! -- Ian GPG Key: http://homepages.picknowl.com.au/imoore/imoore.asc pgppQUGyziEew.pgp Description: PGP signature
Firefox bus error
Hi, I've just finished upgrading my ports after a cvsup a few days ago. Now when I try to start firefox, all I get is % firefox& bus error I did some googling & found this: > i solved the problem i told you about switching CFLAGS from -O2 -pipe -fomit-frame-pointer to a more "standard" -O -pipe > bye > > Eugenio > eugenio.modesti at poste.it Unfortunately that doesn't help, since my CFLAGS is set to -O -pipe anyway. I also tried renaming .mozilla so it could start from scratch, but that just gave the following: % firefox& LoadPlugin: failed to initialize shared library /usr/local/Acrobat5/Browsers/intellinux/nppdf.so [/usr/local/Acrobat5/Browsers/intellinux/nppdf.so: Undefined symbol "XtStrings"] firefox-bin: Fatal IO error 78 (Function not implemented) on X server :0.0. Does anyone have any suggestions? Cheers, -- Ian GPG Key: http://homepages.picknowl.com.au/imoore/imoore.asc pgpyjIBMak9ii.pgp Description: PGP signature
Bus-error hardware or software?
Every once in a while, an httpd (Apache 3.28) child exits with a seg-fault of sorts. I hope someone can tell me whether or not this is hardware-related: asarian-host.net kernel log messages: > 9 10/100BaseTX> port 0xa000-0xa0ff mem 0xda00-0xdaff irq 11 at device 13.0 > on pci0 > pid 15369 (httpd), uid 65534: exited on signal 11 asarian-host.net kernel log messages: > daff irq 11 at device 13.0 on pci0 > pid 1478 (httpd), uid 65534: exited on signal 10 It seems to me a matter of software; a read on a wrong memory address, to be precise. But since the log talks about a device on a pci bus, and one of the signals is a bus error (signal 10), maybe it is hardware after all. I must say, though, that I only ever experience this with the http daemon. The rest is rock-solid. Any diagnostic help is appreciated. Thanks, - Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Resolved: Re: bus error
On Thu, Jun 26, 2003 at 02:41:40PM -0400 David S. Jackson <[EMAIL PROTECTED]> wrote: > On Wed, Jun 25, 2003 at 03:49:19PM -0700 Joshua Oreman <[EMAIL PROTECTED]> wrote: > > > for xinit.core: > > > #0 0x2805826b in memset () from /usr/libexec/ld-elf.so.1 > > > Cannot access memory at address 0xbfbfe6bc. > > > > As I feared. If you've got the developer mentality, forge ahead. > > If not, forget about it :-) > > > > You have to recompile those programs with debugging flags. > > make configure the port, take a look at the software Makefile > > (the one in work/-/), and look for a > > line that starts with CFLAGS=. Add ` -g' (without the quotes, of > > course), to the end. Run make inside the software directory > > (/usr/ports///work/-/). > > Take the newly produced executable (it should be either in the > > directory you ran 'make' in, or one of the subdirectories) and > > run it under gdb (gdb myexecutable). Type `run' at the gdb prompt. > > When it crashes, type `bt'. Send us the output :-) > > Turns out make doesn't finish operating. pkg -r'ed another vim > package, > > This time when I execute it: > > /usr/libexec/ld-elf.so.1: /usr/X11R6/lib/libXi.so.6: invalid file > format. > > Strangely, this happened while in a tty, not an x window. (X > won't start, still.) I wound up removing the XFree86 package and rebuilding the port from scratch. I guess I could have reinstalled the package, too. Anyway, that worked, so far. -- David S. Jackson[EMAIL PROTECTED] =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Comedy, like Medicine, was never meant to be practiced by the general public. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bus error
On Wed, Jun 25, 2003 at 03:49:19PM -0700 Joshua Oreman <[EMAIL PROTECTED]> wrote: > > for xinit.core: > > #0 0x2805826b in memset () from /usr/libexec/ld-elf.so.1 > > Cannot access memory at address 0xbfbfe6bc. > > As I feared. If you've got the developer mentality, forge ahead. > If not, forget about it :-) > > You have to recompile those programs with debugging flags. > make configure the port, take a look at the software Makefile > (the one in work/-/), and look for a > line that starts with CFLAGS=. Add ` -g' (without the quotes, of > course), to the end. Run make inside the software directory > (/usr/ports///work/-/). > Take the newly produced executable (it should be either in the > directory you ran 'make' in, or one of the subdirectories) and > run it under gdb (gdb myexecutable). Type `run' at the gdb prompt. > When it crashes, type `bt'. Send us the output :-) Turns out make doesn't finish operating. pkg -r'ed another vim package, This time when I execute it: /usr/libexec/ld-elf.so.1: /usr/X11R6/lib/libXi.so.6: invalid file format. Strangely, this happened while in a tty, not an x window. (X won't start, still.) -- David S. Jackson[EMAIL PROTECTED] =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Thank goodness modern convenience is a thing of the remote future. -- Pogo, by Walt Kelly ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bus error
On Wed, Jun 25, 2003 at 05:49:30PM -0400 or thereabouts, David S. Jackson wrote: > Joshua Oreman suggested I try "bt" while in gdb looking at the > core files. The output from that command was: > > for vim.core: > > #0 0x2815a26b in memset () from /usr/libexec/ld-elf.so.1 > Cannot access memory at address 0xbfbfe6e0. > > for xinit.core: > #0 0x2805826b in memset () from /usr/libexec/ld-elf.so.1 > Cannot access memory at address 0xbfbfe6bc. As I feared. If you've got the developer mentality, forge ahead. If not, forget about it :-) You have to recompile those programs with debugging flags. make configure the port, take a look at the software Makefile (the one in work/-/), and look for a line that starts with CFLAGS=. Add ` -g' (without the quotes, of course), to the end. Run make inside the software directory (/usr/ports///work/-/). Take the newly produced executable (it should be either in the directory you ran 'make' in, or one of the subdirectories) and run it under gdb (gdb myexecutable). Type `run' at the gdb prompt. When it crashes, type `bt'. Send us the output :-) > > There is no /etc/malloc.conf file. Should there be? It's okay the way it is. -- Josh > > [Sorry about not including the post--I had to get this off the > archives, since I tried Earthlink's Spaminator, and it deleted > everything from freebsd.org Oops.] > > -- > David S. Jackson[EMAIL PROTECTED] > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > I was in Vegas last week. I was at the roulette table, > having a lengthy argument about what I considered an > Odd number. -- Steven Wright ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bus error
Bill Moran <[EMAIL PROTECTED]> wrote: > Can you rule out hardware problems? Possibly a disk going bad? > I hope you've been making backups. You didn't run fsck while > the partition was mounted, did you? If so, umount the > partition and run fsck until it reports no errors and see if > that fixes things. The slice seems to fsck just fine. No errors. But, /mnt/usr1 is a different story though... Oof. -- David S. Jackson[EMAIL PROTECTED] =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Faster, faster, you fool, you fool! -- Bill Cosby ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bus error
Joshua Oreman suggested I try "bt" while in gdb looking at the core files. The output from that command was: for vim.core: #0 0x2815a26b in memset () from /usr/libexec/ld-elf.so.1 Cannot access memory at address 0xbfbfe6e0. for xinit.core: #0 0x2805826b in memset () from /usr/libexec/ld-elf.so.1 Cannot access memory at address 0xbfbfe6bc. There is no /etc/malloc.conf file. Should there be? [Sorry about not including the post--I had to get this off the archives, since I tried Earthlink's Spaminator, and it deleted everything from freebsd.org Oops.] -- David S. Jackson[EMAIL PROTECTED] =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= I was in Vegas last week. I was at the roulette table, having a lengthy argument about what I considered an Odd number. -- Steven Wright ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bus error
David S. Jackson wrote: Hi, First, forgive me if this doesn't come through devoid of html. I'm normally a mutt user, but I'm trying evolution. We'll see how it goes. I'm on a $.%-STABLE system, and I've been experiencing some disk errors; I did an fsck -y on the slice where /usr lives. (I forgot it was /usr when I did this.) Since then, I've received various "program terminated with signal 10. Bus error." problems. Examples are vim and xinit. As you can imagine, I'm eager to fix this so I can get X back. Looking at the core files left behind by X and by vim, I see the following: *** snip *** GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software ... blah blah ... This GDB was configured as "i386-unknown-freebsd" ... (no debugging symbols found)... Core was generated by 'vim'. Program terminated with signal 10. Bus error. Reading symbols from /usr/X11R6/lib/libgtk12.so.2... (no debugging symbols found)...done. Reading symbols from /usr/X11R6/lib/libgdk12.so.2... (no debugging symbols found)...done. Reading symbols from /usr/local/lib/libgmodule12.so.3... (no debugging symbols found)...done. Reading symbols from /usr/local/lib/libglib12.so.3... (no debugging symbols found)...done. Reading symbols from /usr/local/lib/compat/pkg/libintl.so.2... (no debugging symbols found)...done. Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found)...done. #0 0x2815a26b in memset () from /usr/libexec/ld-elf.so.1 (gdb) *** snip *** That was for vim. Here's for xinit: *** snip *** GNU gdb 4.18 blah blah blah Core was generated by 'xinit'. Program terminated with signal 10. Bus error. Reading symbols from /usr/X11R6/lib/libXmu.so.6... (no debugging symbols found)...done. Reading symbols from /usr/X11R6/lib/libXt.so.6... (no debugging symbols found)...done. Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found...done. #0 0x2805826b in memset () from /usr/libexec/ld-elf.so.1 (gdb) *** snip *** I typed all this by hand, so hopefully I have it correct. Notes: this problem is about 48 hours old. So far I've tried remaking ld-elf.so.1 from /usr/src/libexec/rtld-elf and copying ld-elf.so.1 from /usr/obj/usr/src/libexec/rtld-elf to /usr/libexec/, but even from single user runlevel, this was not allowed. I've thought about remaking the system, but I'm thinking that if ld-elf.so is broken, things probably wouldn't make correctly for a new system. Am I wrong on that? I've also thought about reinstalling a binary distribution on top of all this (upgrade from a new 4.8-stable CD), but that's an even bigger risk, I would think. So, what would you gurus do? What should be my next step for trying to salvage my system here? Can you rule out hardware problems? Possibly a disk going bad? I hope you've been making backups. You didn't run fsck while the partition was mounted, did you? If so, umount the partition and run fsck until it reports no errors and see if that fixes things. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
bus error
Hi, First, forgive me if this doesn't come through devoid of html. I'm normally a mutt user, but I'm trying evolution. We'll see how it goes. I'm on a $.%-STABLE system, and I've been experiencing some disk errors; I did an fsck -y on the slice where /usr lives. (I forgot it was /usr when I did this.) Since then, I've received various "program terminated with signal 10. Bus error." problems. Examples are vim and xinit. As you can imagine, I'm eager to fix this so I can get X back. Looking at the core files left behind by X and by vim, I see the following: *** snip *** GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software ... blah blah ... This GDB was configured as "i386-unknown-freebsd" ... (no debugging symbols found)... Core was generated by 'vim'. Program terminated with signal 10. Bus error. Reading symbols from /usr/X11R6/lib/libgtk12.so.2... (no debugging symbols found)...done. Reading symbols from /usr/X11R6/lib/libgdk12.so.2... (no debugging symbols found)...done. Reading symbols from /usr/local/lib/libgmodule12.so.3... (no debugging symbols found)...done. Reading symbols from /usr/local/lib/libglib12.so.3... (no debugging symbols found)...done. Reading symbols from /usr/local/lib/compat/pkg/libintl.so.2... (no debugging symbols found)...done. Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found)...done. #0 0x2815a26b in memset () from /usr/libexec/ld-elf.so.1 (gdb) *** snip *** That was for vim. Here's for xinit: *** snip *** GNU gdb 4.18 blah blah blah Core was generated by 'xinit'. Program terminated with signal 10. Bus error. Reading symbols from /usr/X11R6/lib/libXmu.so.6... (no debugging symbols found)...done. Reading symbols from /usr/X11R6/lib/libXt.so.6... (no debugging symbols found)...done. Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found...done. #0 0x2805826b in memset () from /usr/libexec/ld-elf.so.1 (gdb) *** snip *** I typed all this by hand, so hopefully I have it correct. Notes: this problem is about 48 hours old. So far I've tried remaking ld-elf.so.1 from /usr/src/libexec/rtld-elf and copying ld-elf.so.1 from /usr/obj/usr/src/libexec/rtld-elf to /usr/libexec/, but even from single user runlevel, this was not allowed. I've thought about remaking the system, but I'm thinking that if ld-elf.so is broken, things probably wouldn't make correctly for a new system. Am I wrong on that? I've also thought about reinstalling a binary distribution on top of all this (upgrade from a new 4.8-stable CD), but that's an even bigger risk, I would think. So, what would you gurus do? What should be my next step for trying to salvage my system here? TIA! -- David S. Jackson <[EMAIL PROTECTED]> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bus error
On Mon, Jun 23, 2003 at 01:24:39PM -0400 or thereabouts, David S. Jackson seemed to write: > > I'm afraid I'm getting a nasty error when I try to do some very > fundamental things. Not sure what's back of all the problems. > > For example when I try to start vim or even xinit, I get: > > Jun 23 12:00:12 juno /kernel: pid 2700 (vim), uid 0: exited on signal 10 > > > (I happened to be root at the time, but same applies to any user.) > > > When I try to startx, I get: > > Bus error > > uname -a shows: FreeBSD juno.dsj.net 4.5-STABLE FreeBSD > 4.5-STABLE #7: Sun Apr 28 15:23:53 EDT 2002: > [EMAIL PROTECTED]:/usr/src/sys/compile/JUNO i386 > > I do find .core files for proggies I cannot start, though. I went gdb vim vim.core > and got the following: > > ***snip*** > (no debugging symbols found) > Core was generated by 'vim'. > Program terminated with signal 10, Bus error. > Reading symbo9ls from /usr/X11R6/lib/libgtk12.so.2... > (no debugging symbols found)...done > Reading symbols from /usr/X11R6/lib/libgdk12.so.2... > (no debugging symbols found)...done > Reading symbols from /usr/X11R6/lib/libgmodule12.so.3... > (no debugging symbols found)...done > Reading symbols from /usr/X11R6/lib/libglib12.so.3... > (no debugging symbols found)...done > Reading symbols from /usr/local/lib/compat/pkg/libintl.so.2... > (no debugging symbols found)...done > Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found)...done > #0 0x2815a26b in memset () from /usr/libexec/ld-elf.so.1 > (gdb) Type 'bt', press enter. > > ***snip*** > > Here's the same thing for xinit.core > > ***snip*** > This GDB was configured as "i386-unknown-freebsd"... > (no debugging symbols found)... > Core was generated by 'xinit'. > Program terminated with signal 10, Bus error. > Reading symbols from /usr/X11R6/lib/libXmu.so.6... > (no debugging symbols found)... > Reading symbols from /usr/X11R6/lib/libXt.so.6... > (no debugging symbols found)... > Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found)...done > #0 0x2805826b in memset () from /usr/libexec/ld-elf.so.1 > (gdb) Type 'bt', press enter. > > ***snip*** > > > Mind you, I typed this while looking at the screen of the other > box. Hope I got it correctly. > > Any idea what is back of this? Just clutching at straws here... What does ls -l /etc/malloc.conf say? > > Does it look like some file corruption to ld-elf.so.1? How the > heck do I fix that if so? I tried to remake a kernel a while back > and couldn't even complete that process. (sniff, sniff) > > What type of stuff uses ld-elf.so.1 anyway? Everything? Everything in /usr/local/[s]bin, most things in /usr/bin. -- Josh > > TIA. > > -- > David S. Jackson[EMAIL PROTECTED] > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > I never forget a face, but in your case I'll make > an exception. > -- Groucho Marx > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
bus error
I'm afraid I'm getting a nasty error when I try to do some very fundamental things. Not sure what's back of all the problems. For example when I try to start vim or even xinit, I get: Jun 23 12:00:12 juno /kernel: pid 2700 (vim), uid 0: exited on signal 10 (I happened to be root at the time, but same applies to any user.) When I try to startx, I get: Bus error uname -a shows: FreeBSD juno.dsj.net 4.5-STABLE FreeBSD 4.5-STABLE #7: Sun Apr 28 15:23:53 EDT 2002: [EMAIL PROTECTED]:/usr/src/sys/compile/JUNO i386 I do find .core files for proggies I cannot start, though. I went gdb vim vim.core and got the following: ***snip*** (no debugging symbols found) Core was generated by 'vim'. Program terminated with signal 10, Bus error. Reading symbo9ls from /usr/X11R6/lib/libgtk12.so.2... (no debugging symbols found)...done Reading symbols from /usr/X11R6/lib/libgdk12.so.2... (no debugging symbols found)...done Reading symbols from /usr/X11R6/lib/libgmodule12.so.3... (no debugging symbols found)...done Reading symbols from /usr/X11R6/lib/libglib12.so.3... (no debugging symbols found)...done Reading symbols from /usr/local/lib/compat/pkg/libintl.so.2... (no debugging symbols found)...done Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found)...done #0 0x2815a26b in memset () from /usr/libexec/ld-elf.so.1 (gdb) ***snip*** Here's the same thing for xinit.core ***snip*** This GDB was configured as "i386-unknown-freebsd"... (no debugging symbols found)... Core was generated by 'xinit'. Program terminated with signal 10, Bus error. Reading symbols from /usr/X11R6/lib/libXmu.so.6... (no debugging symbols found)... Reading symbols from /usr/X11R6/lib/libXt.so.6... (no debugging symbols found)... Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found)...done #0 0x2805826b in memset () from /usr/libexec/ld-elf.so.1 (gdb) ***snip*** Mind you, I typed this while looking at the screen of the other box. Hope I got it correctly. Any idea what is back of this? Does it look like some file corruption to ld-elf.so.1? How the heck do I fix that if so? I tried to remake a kernel a while back and couldn't even complete that process. (sniff, sniff) What type of stuff uses ld-elf.so.1 anyway? Everything? TIA. -- David S. Jackson[EMAIL PROTECTED] =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= I never forget a face, but in your case I'll make an exception. -- Groucho Marx ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Bus error - FD or msdos HD mount
hello, i'm beginning in the FreeBSD world, and i can't mount my floppy disk and my Win98 hard disk. i tape: # mount -t msdos /dev/ad0s1 /hdibm or: # mount -t msdos /dev/fd0.1440 /floppy and i get "Bus error" and a core file. my Win98 disk is bootable (only 1 partition - FAT32, 12.6 Go) and connected in master to the primary IDE. my floppy is a classic 1.44 Mo and i want to read MSDOS formated floppies. of course i have the 2 special files in /dev, and i created the mount directories. i have access to these disks with fsck_msdosfs or disklabel. i followed all the procedure to format and mount a new MSDOS floppy disk but i always have this error. i haven't these problems with my CDROM and my bootable FreeBSD disk. for information i can reproduce this error when i try to mount one of my FreeBSD partition as a MSDOS partition ( # mount -t msdos /dev/ad3s1g /tmp ). (i'm under FreeBSD 4.7) does somebody know how to resolve this problem? thank you! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Bus error - FD or msdos HD mount
hello, i'm beginning in the FreeBSD world, and i can't mount my floppy disk and my Win98 hard disk. i tape: # mount -t msdos /dev/ad0s1 /hdibm or: # mount -t msdos /dev/fd0.1440 /floppy and i get "Bus error" and a core file. my Win98 disk is bootable (only 1 partition - FAT32, 12.6 Go) and connected in master to the primary IDE. my floppy is a classic 1.44 Mo and i want to read MSDOS formated floppies. of course i have the 2 special files in /dev, and i created the mount directories. i have access to these disks with fsck_msdosfs or disklabel. i followed all the procedure to format and mount a new MSDOS floppy disk but i always have this error. i haven't these problems with my CDROM and my bootable FreeBSD disk. for information i can reproduce this error when i try to mount one of my FreeBSD partition as a MSDOS partition ( # mount -t msdos /dev/ad3s1g /tmp ). (i'm under FreeBSD 4.7) does somebody know how to resolve this problem? thank you! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Bus error (core dumped) when running pkg_add
On Fri, 27 Sep 2002, Søren Neigaard wrote: > Date: Fri, 27 Sep 2002 19:44:57 +0200 > From: Søren Neigaard <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Bus error (core dumped) when running pkg_add > > If I try to run pkg_add on either a tbz file, tgz file or without > specifying any file, it core dumps. Here is the message: > > Bus error (core dumped) > Sep 27 21:41:06 neigaard /kernel: pid 110 (pkg_add), uid 0: exited on > signal 10 > (core dumped) > > What is this, is it a hardware error? I dont seem to have any other > problems, and I have just installed this 4.6.2 on this machine without > any problems. > > Please help, I don't know what to do. > Since no-one jumped in on this... A bus error is similar to a segfault, I believe. It means an app tried to access some memory outside it's accessible range or tried to access an array element outside the array's dimensions - something of that sort. I believe a 'bus' error means accessing a stack frame not owned by the app, or a bad access inside an owned stack frame? The pkg_* tools are pretty widely used and tested. This being the case I'd guess this may be a hardware error, possibly bad RAM? This is speculation at best. Possibly re-compile pkg_add with debug support and run it in a debugger or try some different memory? Which FBSD version are you runnnig? Arent there issues with the pkg_* tools and the tbz/tgz file types at the moment? Dunno, maybe you found a bug ? ;-) Good luck! JB # John Bleichert # http://vonbek.dhs.org/latest.jpg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Bus error (core dumped) when running pkg_add
If I try to run pkg_add on either a tbz file, tgz file or without specifying any file, it core dumps. Here is the message: Bus error (core dumped) Sep 27 21:41:06 neigaard /kernel: pid 110 (pkg_add), uid 0: exited on signal 10 (core dumped) What is this, is it a hardware error? I dont seem to have any other problems, and I have just installed this 4.6.2 on this machine without any problems. Please help, I don't know what to do. -- Med venlig hilsen/Best regards, Søren Neigaard mailto:[EMAIL PROTECTED] -- "Once you start down the dark path, forever will it dominate your destiny. Consume you it wil." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
