Re: HELP! core dumps: install, mtree, et cetera all of the sudden after portmaster security/cyrus-sasl2
Am 08/16/12 21:44, schrieb Garrett Cooper: > On Thu, Aug 16, 2012 at 8:33 AM, Hartmann, O. > wrote: >> >> I ran into a very delicate and nasty situation. > > ... > >> On both FBSD 10 boxes, the installation of the port security/cyrus-sasl2 >> got corrupted by "install" and/or "mtree" dumping core and signalling >> SIGNAL 11. Booting into multiuser mode is impossible, login core dumps >> SIGNAL 11, many other daemons, too. The only way is to boot into single >> user mode. > > I'm not drawing a correlation between this and unrelated coredumping > processes. Me neither, I report this for completeness, since I'm not a OS developer, such a behaviour could hint/indicate people who are involved in the OS development, what is going on. Sorry when I'm trying to be too precise (precise as precise I can be without the exact terminology!). > >> An installation failed due to pkg(ng) was missing libarchive.so via >> portmaster or via core dumping install(1). By installing on one box, my >> home box, port security/cyrus-sasl2 manually, luckily install(1) and >> mtree(1) didn't coredump and it worked - and this precedure rescued me. >> But on my lab's development box, it doesn't work! > > Don't make delete-old-lib unless you have it moved off to compat > directories, or have rebuilt everything using the new libarchive. I didn't! As I wrote before, this mess happened on ALL(!) freeBSD 10.0-CURRENT boxes in the very same way when I updated/reinstalled security/cyrus-sasl2. Moreover: I can reproduce this on all boxes. All my boxes use OpenLDAP as a backend with SASL2 enabled (not used so far). > >> On this specific box, where this nasty problem also occured the same way >> by simply recompiling everything for port www/apache22, including the >> reinstallation of port security/cyrus-sasl2. Nearly every binary is >> suddenly coredumping (as on the home box). login, vi, install, devfs, >> syslogd, mtree, id, find ... a whole lot of binaries seem to be >> compromised by something I do not see (libsasl2.so perhaps?). > > truss the binaries to figure out exactly what's going wrong. I will try, but when this errative coredumps of binaries occur, nothing works properly that is using any kinf of dynamical loaded library! Only the binaries (static?) from /resucue/* do their work. > > A lot of this lost effort could be avoided (like others have posted on > the list more than once), by having a centralized package distribution > server, and by having VMs or jails and keeping snapshots with > pre-upgrade state on the package building machine to avoid "dead in > the water scenarios" like you're in right now. Yes, I'm working on this. it seems, that it becomes more relevant since I realized that FreeBSD suffers sometimes from misleaded ports or ports which suddenly are marked BROKEN and do not get compiled ... > >> I tried to help myself via copying /rescue/vi to /usr/bin/vi to have at >> least a working vi. But in /rescue, I can not find install or mtree. I'm >> not familiar with the sophisticated ways of /rescue. Where are >> install(1) and mtree(1)? > > I ran into this issue too a little while ago. I basically gave up on > recovering a VM and nuked and repaved it using a LiveCD with a chroot, > some cp -p'ing, etc. But yes.. it would be nice if I could have > recovered the system at least with a static toolchain: cc, binutils > [equivalent], mtree, install, etc. This is how I recovered the nasty broken box. The other one was easy to recover by reinstalling security/cyrus-sasl2. I'm quite sure that there is something very foul with something in LDAP or SASL2, since I can reproduce that proplem. I saw that rtdl-elf has got some quirks these days, I will try to go behind the date/version of the source tree when it was committed and check whether this is the problem. > > ... > >> Disabling this pkgng tag leads to reinstallation of missing packages, >> which are store in the pkgng sqlite format and not as ASCII anymore, but >> then I get >> /var/runld-elf.so.hints: No such file or directory >> Error: shared library "iconv.3" does not exist. > > service ldconfig start ? Yes ... sorry ... in the heat of the fight I forgot ... but it doesn't make the problem go away. > >> But most of the libs have never been touch! So what is the loader >> complaining about? > > ... > >> I tried to find rescue images and a rescue DVD of a snap shot server, >> but there is no way to crawl through the informations on the web pages >> towards a snapshot. All folders end up in 2011 and highly outdated >> (www.free
Re: HELP! core dumps: install, mtree, et cetera all of the sudden after portmaster security/cyrus-sasl2
On Fri, Aug 17, 2012 at 09:44:40AM +0200, Hartmann, O. wrote: > >> An installation failed due to pkg(ng) was missing libarchive.so via > > > > There is pkg-static for recovering in this type of situation. > > Oh ... I'm new to pkg(ng). > No worries. It is a nice thing to know about, since after a big shlib bump during an upgrade, if all else is broken, you can still at least get /rescue stuff and pkg-static to upgrade third party software. > >> If someone has some hints how to recompile the sources with an emergency > >> booted disk, I highly appreciate some desater advice. Maybe the release > >> of FreeBSD-10-CURRENT sources I compiled do have accidentally a nasty > >> bug, so it would be nice to update the sources and have a complete > >> recompilation done. > >> > > > > If you can get booted into a recovery medium, you can mount /usr/src and > > /usr/obj from the hosed system, and should be able to > > installworld/installkernel into the hosed system with DESTDIR set. > > > > I do this the very moment with the RELEASE CD I found at allbsd.org for > the most recent FBSD 10.0-CURRENT as from 16.08.2012. I try to build the > sources and install them into the mounted DESTDIR. > I have lately been creating memstick images for this exact type of thing. On -CURRENT and 9-STABLE, you can do: # make -C /usr/src buildworld buildkernel # make -C /usr/src/release NOSRC=yes NODOCS=yes NOPORTS=yes memstick Then take the resulting memory stick image to use for recovery. Glen ___ 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: HELP! core dumps: install, mtree, et cetera all of the sudden after portmaster security/cyrus-sasl2
On 08/16/12 17:44, Glen Barber wrote: > On Thu, Aug 16, 2012 at 05:33:20PM +0200, Hartmann, O. wrote: >> >> I ran into a very delicate and nasty situation. >> >> On several boxes, FreeBSD 9.1-PRE and FreeBSD 10-CURRENT (build of >> CURRENT sources from yesterday, r239295 Wed August 15 17:04:51 CEST 2012 >> amd64, I had to recompile all requirements of port Apache22, since after >> the port update it core dumped. >> >> On FreeBSD 9.1-PRE, with pkg(ng), things went well. Recompilation and >> installation of all "portmaster -f apache-2.2" requirements went perfect. >> >> On both FreeBSD 10-CURRENT boxes it ended up in a mess, all of a >> sudden(!), while reinstalling port security/cyrus-sasl2, things started >> to fail in a dramatik way! >> >> On both FBSD 10 boxes, the installation of the port security/cyrus-sasl2 >> got corrupted by "install" and/or "mtree" dumping core and signalling >> SIGNAL 11. Booting into multiuser mode is impossible, login core dumps >> SIGNAL 11, many other daemons, too. The only way is to boot into single >> user mode. >> >> An installation failed due to pkg(ng) was missing libarchive.so via > > There is pkg-static for recovering in this type of situation. Oh ... I'm new to pkg(ng). > >> portmaster or via core dumping install(1). By installing on one box, my >> home box, port security/cyrus-sasl2 manually, luckily install(1) and >> mtree(1) didn't coredump and it worked - and this precedure rescued me. >> But on my lab's development box, it doesn't work! >> >> On this specific box, where this nasty problem also occured the same way >> by simply recompiling everything for port www/apache22, including the >> reinstallation of port security/cyrus-sasl2. Nearly every binary is >> suddenly coredumping (as on the home box). login, vi, install, devfs, >> syslogd, mtree, id, find ... a whole lot of binaries seem to be >> compromised by something I do not see (libsasl2.so perhaps?). >> >> I tried to help myself via copying /rescue/vi to /usr/bin/vi to have at >> least a working vi. But in /rescue, I can not find install or mtree. I'm >> not familiar with the sophisticated ways of /rescue. Where are >> install(1) and mtree(1)? >> >> Trying to reinstall security/cyrus-sasl2 from single-user fails due >> install coredumps. pkg(ng) fails due to missing libpkg.so.5 and even >> rejects being reinstalled. But /usr/local/lib/libpkg.so.0 is even there! >> Disabling the use of pkg with commenting out WITH_PKGNG=yes in >> /etc/make.conf leads to the above issues with mtree and install. >> Disabling this pkgng tag leads to reinstallation of missing packages, >> which are store in the pkgng sqlite format and not as ASCII anymore, but >> then I get >> /var/runld-elf.so.hints: No such file or directory > > Is this a typo, or literal transcription? (The missing "/" between > 'run' and 'ld-elf.so.hints', that is.) A typo, sorry. I had to type it from the screen of the broken box to the laptop. > >> Error: shared library "iconv.3" does not exist. >> >> But most of the libs have never been touch! So what is the loader >> complaining about? >> >> Well, I'm floating like a dead man in the water and I'm glad that one >> box survided although suffering from the same symptomes. >> >> I tried to find rescue images and a rescue DVD of a snap shot server, >> but there is no way to crawl through the informations on the web pages >> towards a snapshot. All folders end up in 2011 and highly outdated >> (www.freebsd.org, I didn't look at mirrors since I thought the main >> server carries the most recent stuff). This isn't funny. No lead, no >> hint, even in the download section. >> > > Yes, I have been complaining about this for a while now... This is a so unneccessary issue. Why are people bothering themselfs with hiding a bit of information? If one isn't a cold-blood developer aware of all the neat knobs of FBSD and where to ask and where to look, a novice or not-so-well-informed guy like me run into frustration. The main page should have a hint present, where to find the newest stuff. Leaving the officiela page the way it is at the moment in this specific issue, it looks a bit "unmaintained" ... > >> If someone has some hints how to recompile the sources with an emergency >> booted disk, I highly appreciate some desater advice. Maybe the release >> of FreeBSD-10-CURRENT sources I compiled do have accidentally a nasty >> bug, so it would be nice to u
Re: HELP! core dumps: install, mtree, et cetera all of the sudden after portmaster security/cyrus-sasl2
On Thu, Aug 16, 2012 at 8:33 AM, Hartmann, O. wrote: > > I ran into a very delicate and nasty situation. ... > On both FBSD 10 boxes, the installation of the port security/cyrus-sasl2 > got corrupted by "install" and/or "mtree" dumping core and signalling > SIGNAL 11. Booting into multiuser mode is impossible, login core dumps > SIGNAL 11, many other daemons, too. The only way is to boot into single > user mode. I'm not drawing a correlation between this and unrelated coredumping processes. > An installation failed due to pkg(ng) was missing libarchive.so via > portmaster or via core dumping install(1). By installing on one box, my > home box, port security/cyrus-sasl2 manually, luckily install(1) and > mtree(1) didn't coredump and it worked - and this precedure rescued me. > But on my lab's development box, it doesn't work! Don't make delete-old-lib unless you have it moved off to compat directories, or have rebuilt everything using the new libarchive. > On this specific box, where this nasty problem also occured the same way > by simply recompiling everything for port www/apache22, including the > reinstallation of port security/cyrus-sasl2. Nearly every binary is > suddenly coredumping (as on the home box). login, vi, install, devfs, > syslogd, mtree, id, find ... a whole lot of binaries seem to be > compromised by something I do not see (libsasl2.so perhaps?). truss the binaries to figure out exactly what's going wrong. A lot of this lost effort could be avoided (like others have posted on the list more than once), by having a centralized package distribution server, and by having VMs or jails and keeping snapshots with pre-upgrade state on the package building machine to avoid "dead in the water scenarios" like you're in right now. > I tried to help myself via copying /rescue/vi to /usr/bin/vi to have at > least a working vi. But in /rescue, I can not find install or mtree. I'm > not familiar with the sophisticated ways of /rescue. Where are > install(1) and mtree(1)? I ran into this issue too a little while ago. I basically gave up on recovering a VM and nuked and repaved it using a LiveCD with a chroot, some cp -p'ing, etc. But yes.. it would be nice if I could have recovered the system at least with a static toolchain: cc, binutils [equivalent], mtree, install, etc. ... > Disabling this pkgng tag leads to reinstallation of missing packages, > which are store in the pkgng sqlite format and not as ASCII anymore, but > then I get > /var/runld-elf.so.hints: No such file or directory > Error: shared library "iconv.3" does not exist. service ldconfig start ? > But most of the libs have never been touch! So what is the loader > complaining about? ... > I tried to find rescue images and a rescue DVD of a snap shot server, > but there is no way to crawl through the informations on the web pages > towards a snapshot. All folders end up in 2011 and highly outdated > (www.freebsd.org, I didn't look at mirrors since I thought the main > server carries the most recent stuff). This isn't funny. No lead, no > hint, even in the download section. > > If someone has some hints how to recompile the sources with an emergency > booted disk, I highly appreciate some desater advice. Maybe the release > of FreeBSD-10-CURRENT sources I compiled do have accidentally a nasty > bug, so it would be nice to update the sources and have a complete > recompilation done. > > Thanks in advance, Simply put: fix your infrastructure (as this isn't the first time you have complained about infrastructure issues on the MLs). A lot of these issues should not be issues if you set up your infrastructure properly to deal with building things only once, backup packages before installation, you had snapshots of your system, etc. This will help you avoid administration pain, and hopefully will result in less duplicated work. Cheers, -Garrett ___ 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: HELP! core dumps: install, mtree, et cetera all of the sudden after portmaster security/cyrus-sasl2
On Thu, Aug 16, 2012 at 11:33 AM, O. Hartmann wrote: > I ran into a very delicate and nasty situation. Please don't cross-post / double-post. Thanks, -Garrett ___ 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"
HELP! core dumps: install, mtree, et cetera all of the sudden after portmaster security/cyrus-sasl2
I ran into a very delicate and nasty situation. On several boxes, FreeBSD 9.1-PRE and FreeBSD 10-CURRENT (build of CURRENT sources from yesterday, r239295 Wed August 15 17:04:51 CEST 2012 amd64, I had to recompile all requirements of port Apache22, since after the port update it core dumped. On FreeBSD 9.1-PRE, with pkg(ng), things went well. Recompilation and installation of all "portmaster -f apache-2.2" requirements went perfect. On both FreeBSD 10-CURRENT boxes it ended up in a mess, all of a sudden(!), while reinstalling port security/cyrus-sasl2, things started to fail in a dramatik way! On both FBSD 10 boxes, the installation of the port security/cyrus-sasl2 got corrupted by "install" and/or "mtree" dumping core and signalling SIGNAL 11. Booting into multiuser mode is impossible, login core dumps SIGNAL 11, many other daemons, too. The only way is to boot into single user mode. An installation failed due to pkg(ng) was missing libarchive.so via portmaster or via core dumping install(1). By installing on one box, my home box, port security/cyrus-sasl2 manually, luckily install(1) and mtree(1) didn't coredump and it worked - and this precedure rescued me. But on my lab's development box, it doesn't work! On this specific box, where this nasty problem also occured the same way by simply recompiling everything for port www/apache22, including the reinstallation of port security/cyrus-sasl2. Nearly every binary is suddenly coredumping (as on the home box). login, vi, install, devfs, syslogd, mtree, id, find ... a whole lot of binaries seem to be compromised by something I do not see (libsasl2.so perhaps?). I tried to help myself via copying /rescue/vi to /usr/bin/vi to have at least a working vi. But in /rescue, I can not find install or mtree. I'm not familiar with the sophisticated ways of /rescue. Where are install(1) and mtree(1)? Trying to reinstall security/cyrus-sasl2 from single-user fails due install coredumps. pkg(ng) fails due to missing libpkg.so.5 and even rejects being reinstalled. But /usr/local/lib/libpkg.so.0 is even there! Disabling the use of pkg with commenting out WITH_PKGNG=yes in /etc/make.conf leads to the above issues with mtree and install. Disabling this pkgng tag leads to reinstallation of missing packages, which are store in the pkgng sqlite format and not as ASCII anymore, but then I get /var/runld-elf.so.hints: No such file or directory Error: shared library "iconv.3" does not exist. But most of the libs have never been touch! So what is the loader complaining about? Well, I'm floating like a dead man in the water and I'm glad that one box survided although suffering from the same symptomes. I tried to find rescue images and a rescue DVD of a snap shot server, but there is no way to crawl through the informations on the web pages towards a snapshot. All folders end up in 2011 and highly outdated (www.freebsd.org, I didn't look at mirrors since I thought the main server carries the most recent stuff). This isn't funny. No lead, no hint, even in the download section. If someone has some hints how to recompile the sources with an emergency booted disk, I highly appreciate some desater advice. Maybe the release of FreeBSD-10-CURRENT sources I compiled do have accidentally a nasty bug, so it would be nice to update the sources and have a complete recompilation done. Thanks in advance, oh signature.asc Description: OpenPGP digital signature
Re: HELP! core dumps: install, mtree, et cetera all of the sudden after portmaster security/cyrus-sasl2
On 8/16/2012 10:33 AM, Hartmann, O. wrote: > I tried to find rescue images and a rescue DVD of a snap shot server, > but there is no way to crawl through the informations on the web pages > towards a snapshot. All folders end up in 2011 and highly outdated > (www.freebsd.org, I didn't look at mirrors since I thought the main > server carries the most recent stuff). This isn't funny. No lead, no > hint, even in the download section. http://pub.allbsd.org/FreeBSD-snapshots/ Bryan ___ 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: HELP! core dumps: install, mtree, et cetera all of the sudden after portmaster security/cyrus-sasl2
On Thu, Aug 16, 2012 at 05:33:20PM +0200, Hartmann, O. wrote: > > I ran into a very delicate and nasty situation. > > On several boxes, FreeBSD 9.1-PRE and FreeBSD 10-CURRENT (build of > CURRENT sources from yesterday, r239295 Wed August 15 17:04:51 CEST 2012 > amd64, I had to recompile all requirements of port Apache22, since after > the port update it core dumped. > > On FreeBSD 9.1-PRE, with pkg(ng), things went well. Recompilation and > installation of all "portmaster -f apache-2.2" requirements went perfect. > > On both FreeBSD 10-CURRENT boxes it ended up in a mess, all of a > sudden(!), while reinstalling port security/cyrus-sasl2, things started > to fail in a dramatik way! > > On both FBSD 10 boxes, the installation of the port security/cyrus-sasl2 > got corrupted by "install" and/or "mtree" dumping core and signalling > SIGNAL 11. Booting into multiuser mode is impossible, login core dumps > SIGNAL 11, many other daemons, too. The only way is to boot into single > user mode. > > An installation failed due to pkg(ng) was missing libarchive.so via There is pkg-static for recovering in this type of situation. > portmaster or via core dumping install(1). By installing on one box, my > home box, port security/cyrus-sasl2 manually, luckily install(1) and > mtree(1) didn't coredump and it worked - and this precedure rescued me. > But on my lab's development box, it doesn't work! > > On this specific box, where this nasty problem also occured the same way > by simply recompiling everything for port www/apache22, including the > reinstallation of port security/cyrus-sasl2. Nearly every binary is > suddenly coredumping (as on the home box). login, vi, install, devfs, > syslogd, mtree, id, find ... a whole lot of binaries seem to be > compromised by something I do not see (libsasl2.so perhaps?). > > I tried to help myself via copying /rescue/vi to /usr/bin/vi to have at > least a working vi. But in /rescue, I can not find install or mtree. I'm > not familiar with the sophisticated ways of /rescue. Where are > install(1) and mtree(1)? > > Trying to reinstall security/cyrus-sasl2 from single-user fails due > install coredumps. pkg(ng) fails due to missing libpkg.so.5 and even > rejects being reinstalled. But /usr/local/lib/libpkg.so.0 is even there! > Disabling the use of pkg with commenting out WITH_PKGNG=yes in > /etc/make.conf leads to the above issues with mtree and install. > Disabling this pkgng tag leads to reinstallation of missing packages, > which are store in the pkgng sqlite format and not as ASCII anymore, but > then I get > /var/runld-elf.so.hints: No such file or directory Is this a typo, or literal transcription? (The missing "/" between 'run' and 'ld-elf.so.hints', that is.) > Error: shared library "iconv.3" does not exist. > > But most of the libs have never been touch! So what is the loader > complaining about? > > Well, I'm floating like a dead man in the water and I'm glad that one > box survided although suffering from the same symptomes. > > I tried to find rescue images and a rescue DVD of a snap shot server, > but there is no way to crawl through the informations on the web pages > towards a snapshot. All folders end up in 2011 and highly outdated > (www.freebsd.org, I didn't look at mirrors since I thought the main > server carries the most recent stuff). This isn't funny. No lead, no > hint, even in the download section. > Yes, I have been complaining about this for a while now... > If someone has some hints how to recompile the sources with an emergency > booted disk, I highly appreciate some desater advice. Maybe the release > of FreeBSD-10-CURRENT sources I compiled do have accidentally a nasty > bug, so it would be nice to update the sources and have a complete > recompilation done. > If you can get booted into a recovery medium, you can mount /usr/src and /usr/obj from the hosed system, and should be able to installworld/installkernel into the hosed system with DESTDIR set. Glen ___ 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"
HELP! core dumps: install, mtree, et cetera all of the sudden after portmaster security/cyrus-sasl2
I ran into a very delicate and nasty situation. On several boxes, FreeBSD 9.1-PRE and FreeBSD 10-CURRENT (build of CURRENT sources from yesterday, r239295 Wed August 15 17:04:51 CEST 2012 amd64, I had to recompile all requirements of port Apache22, since after the port update it core dumped. On FreeBSD 9.1-PRE, with pkg(ng), things went well. Recompilation and installation of all "portmaster -f apache-2.2" requirements went perfect. On both FreeBSD 10-CURRENT boxes it ended up in a mess, all of a sudden(!), while reinstalling port security/cyrus-sasl2, things started to fail in a dramatik way! On both FBSD 10 boxes, the installation of the port security/cyrus-sasl2 got corrupted by "install" and/or "mtree" dumping core and signalling SIGNAL 11. Booting into multiuser mode is impossible, login core dumps SIGNAL 11, many other daemons, too. The only way is to boot into single user mode. An installation failed due to pkg(ng) was missing libarchive.so via portmaster or via core dumping install(1). By installing on one box, my home box, port security/cyrus-sasl2 manually, luckily install(1) and mtree(1) didn't coredump and it worked - and this precedure rescued me. But on my lab's development box, it doesn't work! On this specific box, where this nasty problem also occured the same way by simply recompiling everything for port www/apache22, including the reinstallation of port security/cyrus-sasl2. Nearly every binary is suddenly coredumping (as on the home box). login, vi, install, devfs, syslogd, mtree, id, find ... a whole lot of binaries seem to be compromised by something I do not see (libsasl2.so perhaps?). I tried to help myself via copying /rescue/vi to /usr/bin/vi to have at least a working vi. But in /rescue, I can not find install or mtree. I'm not familiar with the sophisticated ways of /rescue. Where are install(1) and mtree(1)? Trying to reinstall security/cyrus-sasl2 from single-user fails due install coredumps. pkg(ng) fails due to missing libpkg.so.5 and even rejects being reinstalled. But /usr/local/lib/libpkg.so.0 is even there! Disabling the use of pkg with commenting out WITH_PKGNG=yes in /etc/make.conf leads to the above issues with mtree and install. Disabling this pkgng tag leads to reinstallation of missing packages, which are store in the pkgng sqlite format and not as ASCII anymore, but then I get /var/runld-elf.so.hints: No such file or directory Error: shared library "iconv.3" does not exist. But most of the libs have never been touch! So what is the loader complaining about? Well, I'm floating like a dead man in the water and I'm glad that one box survided although suffering from the same symptomes. I tried to find rescue images and a rescue DVD of a snap shot server, but there is no way to crawl through the informations on the web pages towards a snapshot. All folders end up in 2011 and highly outdated (www.freebsd.org, I didn't look at mirrors since I thought the main server carries the most recent stuff). This isn't funny. No lead, no hint, even in the download section. If someone has some hints how to recompile the sources with an emergency booted disk, I highly appreciate some desater advice. Maybe the release of FreeBSD-10-CURRENT sources I compiled do have accidentally a nasty bug, so it would be nice to update the sources and have a complete recompilation done. Thanks in advance, oh ___ 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: Chromium 19 core dumps on launch...
George Liaskos writes: > On Mon, Jun 11, 2012 at 3:04 AM, Keith Seyffarth wrote: >> >> Friday I installed Chromium again because it would be nice to have a >> browser to test in other than Firefox and Opera. It was installed using >> portinstall -R chromium, which *appeared* to function properly. >> >> However, trying to run chrome results in: >> pid 50993 (chrome), uid 1001: exited on signal 11 (core dumped) >> >> >From what I found online, it looked like I may have been encountering an >> issue with devel/google-perftools, but on reinstall was able to confirm >> that this is building with gcc not clang. >> >> I have also removed my ~/.config/chromium directory with no change in >> behavior. >> >> >> >> Not sure if it's relevant, but the last version of Chromium that was >> *functional* for me was 12. Versions 13-16 didn't support loading web >> pages (the browser would launch, but if I entered a URL in the address >> bar, I could leave the browser running overnight and it still wouldn't >> have started loading a page). Then when 17 and 18 wouldn't even compile >> (marked ignore), I just removed package. > > Please try 19.0.1084.56_1, devel/google-perftools is not a dependency > of chromium anymore. Thanks, George. Upgrading from chromium-19.0.1084.52_2 to chromium-19.0.1084.56_1 (and removing google-perftools) will allow Chromium to launch. However, it can't load many pages. For example: http://tools.google.com/chrome/intl/en/welcome.html http://www.alexa.com/ https://support.google.com/chrome/bin/answer.py?hl=en&answer=1270364&p=e_deadjim http://www.atlatl.com/ https://support.google.com/chrome/bin/answer.py?hl=en&answer=95669&p=e_awsnap chrome://chrome/settings/ and http://www.mariahschallenge.com/ eventually give a "the page has become unresponsive" error. But pages like: http://www.amazon.com/ http://www.google.com/ http://www.firsttankguide.net/ and http://www.visitphilipsburg.com/ load right away. Also, when you close the browser, either by closing the last tab, closing the window, or selecting "Exit" from the tools menu, it doesn't release memory or terminate the process, it just gets rid of the window... It looks like the process hangs around until you kill it. I've tried deleting the profile files again as well, with the same response. Any further ideas? Keith ___ 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: Chromium 19 core dumps on launch...
On Mon, Jun 11, 2012 at 3:04 AM, Keith Seyffarth wrote: > > Friday I installed Chromium again because it would be nice to have a > browser to test in other than Firefox and Opera. It was installed using > portinstall -R chromium, which *appeared* to function properly. > > However, trying to run chrome results in: > pid 50993 (chrome), uid 1001: exited on signal 11 (core dumped) > > >From what I found online, it looked like I may have been encountering an > issue with devel/google-perftools, but on reinstall was able to confirm > that this is building with gcc not clang. > > I have also removed my ~/.config/chromium directory with no change in > behavior. > > > > Not sure if it's relevant, but the last version of Chromium that was > *functional* for me was 12. Versions 13-16 didn't support loading web > pages (the browser would launch, but if I entered a URL in the address > bar, I could leave the browser running overnight and it still wouldn't > have started loading a page). Then when 17 and 18 wouldn't even compile > (marked ignore), I just removed package. Please try 19.0.1084.56_1, devel/google-perftools is not a dependency of chromium anymore. Regards, George ___ 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"
Chromium 19 core dumps on launch...
Friday I installed Chromium again because it would be nice to have a browser to test in other than Firefox and Opera. It was installed using portinstall -R chromium, which *appeared* to function properly. However, trying to run chrome results in: pid 50993 (chrome), uid 1001: exited on signal 11 (core dumped) >From what I found online, it looked like I may have been encountering an issue with devel/google-perftools, but on reinstall was able to confirm that this is building with gcc not clang. I have also removed my ~/.config/chromium directory with no change in behavior. Not sure if it's relevant, but the last version of Chromium that was *functional* for me was 12. Versions 13-16 didn't support loading web pages (the browser would launch, but if I entered a URL in the address bar, I could leave the browser running overnight and it still wouldn't have started loading a page). Then when 17 and 18 wouldn't even compile (marked ignore), I just removed package. Looking for suggestions on getting Chromium to at least launch... ___ 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: guile-1.8.6 build core dumps (autoconf issue ?)
Mel Flynn wrote:
On Thursday 02 April 2009 03:01:53 manish jain wrote:
Hi Mel,
Sorry, I was away for work.
Here is what I think you want :
/usr/ports/lang/guile # make -C /usr/ports/lang/guile -V CONFIGURE_ENV
-V CONFIGURE_ARGS
CPPFLAGS="-I/usr/local/include" LDFLAGS="-L/usr/local/lib"
SHELL=/bin/sh CONFIG_SHELL=/bin/sh MAKE=gmake
AUTOCONF=/usr/local/bin/autoconf-2.62
AUTOHEADER=/usr/local/bin/autoheader-2.62
AUTOIFNAMES=/usr/local/bin/ifnames-2.62
AUTOM4TE=/usr/local/bin/autom4te-2.62
AUTORECONF=/usr/local/bin/autoreconf-2.62
AUTOSCAN=/usr/local/bin/autoscan-2.62
AUTOUPDATE=/usr/local/bin/autoupdate-2.62 AUTOCONF_VERSION=262
lt_cv_sys_max_cmd_len=262144
--prefix=/usr/local ${_LATE_CONFIGURE_ARGS}
Hmmm...last straw:
find /usr/local -name '*.la' -exec grep -- '-llthread' {} +
To explain: something guile needs is built with linux-threads yet this is not
correctly handled and the resulting binaries are flawed, most likely because
another library that guile needs uses FreeBSD native threads.
On FreeBSD threaded linking is done with -pthread linker flag which pulls in
the correct threading library (on 7.0 and above libthr, on 6.x and earlier
libpthread).
Hi Mel,
There is no output.
/root # find /usr/local -name '*.la' -exec grep -- '-llthread' {} +
/root #
--
Thank you and Regards
Manish Jain
invalid.poin...@gmail.com
+91-99830-62246
___
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: guile-1.8.6 build core dumps (autoconf issue ?)
On Thursday 02 April 2009 03:01:53 manish jain wrote:
> Hi Mel,
>
> Sorry, I was away for work.
>
> Here is what I think you want :
>
> /usr/ports/lang/guile # make -C /usr/ports/lang/guile -V CONFIGURE_ENV
> -V CONFIGURE_ARGS
> CPPFLAGS="-I/usr/local/include" LDFLAGS="-L/usr/local/lib"
> SHELL=/bin/sh CONFIG_SHELL=/bin/sh MAKE=gmake
> AUTOCONF=/usr/local/bin/autoconf-2.62
> AUTOHEADER=/usr/local/bin/autoheader-2.62
> AUTOIFNAMES=/usr/local/bin/ifnames-2.62
> AUTOM4TE=/usr/local/bin/autom4te-2.62
> AUTORECONF=/usr/local/bin/autoreconf-2.62
> AUTOSCAN=/usr/local/bin/autoscan-2.62
> AUTOUPDATE=/usr/local/bin/autoupdate-2.62 AUTOCONF_VERSION=262
> lt_cv_sys_max_cmd_len=262144
> --prefix=/usr/local ${_LATE_CONFIGURE_ARGS}
Hmmm...last straw:
find /usr/local -name '*.la' -exec grep -- '-llthread' {} +
To explain: something guile needs is built with linux-threads yet this is not
correctly handled and the resulting binaries are flawed, most likely because
another library that guile needs uses FreeBSD native threads.
On FreeBSD threaded linking is done with -pthread linker flag which pulls in
the correct threading library (on 7.0 and above libthr, on 6.x and earlier
libpthread).
--
Mel
___
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: guile-1.8.6 build core dumps (autoconf issue ?)
On Tuesday 31 March 2009 19:30:59 manish jain wrote: > Mel Flynn wrote: > > On Tuesday 31 March 2009 19:02:56 manish jain wrote: > >> Mel Flynn wrote: > >>> On Tuesday 31 March 2009 08:15:56 manish jain wrote: > >>>> Hi, > >>>> > >>>> I portsnapped the lastest tarball a couple of days back. Doing a build > >>>> > >>>> in lang/guile (1.8.6) core dumps with the following message : > >>>>> Making all in libguile > >>>>> gmake[2]: Entering directory > >>>>> `/usr/ports/lang/guile/work/guile-1.8.6/libguile' cd .. && /bin/sh > >>>>> ./config.status libguile/Makefile depfiles > >>>>> config.status: creating libguile/Makefile > >>>>> config.status: executing depfiles commands > >>>>> gmake[2]: Leaving directory > >>>>> `/usr/ports/lang/guile/work/guile-1.8.6/libguile' gmake[2]: Entering > >>>>> directory `/usr/ports/lang/guile/work/guile-1.8.6/libguile' > >>>>> Generating libpath.h... > >>>>> sed < ./version.h.in > version.h.tmp \ > >>>>> -e s:@-GUILE_MAJOR_VERSION-@:1: \ > >>>>> -e s:@-GUILE_MINOR_VERSION-@:8: \ > >>>>> -e s:@-GUILE_MICRO_VERSION-@:6: > >>>>> mv version.h.tmp version.h > >>>>> if [ "no" = "yes" ]; then \ > >>>>> cc -DHAVE_CONFIG_H -I.. -I.. -I.. -c -o gen-scmconfig.o > >>>>> gen-scmconfig.c; \ else \ > >>>>> cc -DHAVE_CONFIG_H -I.. -I.. -I.. > >>>>> -I/usr/local/include -O2 > >>>>> -fno-strict-aliasing -pipe -Wall -Wmissing-prototypes -Werror -c -o > >>>>> gen-scmconfig.o gen-scmconfig.c; \ fi > >>>>> if [ "no" = "yes" ]; then \ > >>>>> cc -o gen-scmconfig gen-scmconfig.o; \ > >>>>> else \ > >>>>> /bin/sh ../libtool --tag=CC --mode=link cc -O2 > >>>>> -fno-strict-aliasing -pipe -Wall -Wmissing-prototypes -Werror > >>>>> -L/usr/local/lib -o > >>>>> gen-scmconfig gen-scmconfig.o -llthread -lgmp -lcrypt -lm -lltdl ; \ > >>>>> fi libtool: link: cc -O2 -fno-strict-aliasing -pipe -Wall > >>>>> -Wmissing-prototypes -Werror -o gen-scmconfig gen-scmconfig.o > >>>>> -L/usr/local/lib -llthread /usr/local/lib/libgmp.so -lcrypt -lm > >>> > >>> vs mine: > >>> libtool: link: /usr/local/libexec/ccache/world-cc -O2 > >>> -fno-strict-aliasing - pipe -Wall -Wmissing-prototypes -Werror -o > >>> gen-scmconfig gen-scmconfig.o - L/usr/local/lib > >>> /usr/local/lib/libgmp.so -lcrypt -lm /usr/local/lib/libltdl.so > >>> -Wl,-rpath -Wl,/usr/local/lib -Wl,-rpath -Wl,/usr/local/lib > >>> > >>> Where does -llthread come from? > >> > >> Hi Mel, > >> > >> I can't really answer the question. I just ran 'make install clean'. I > >> am attaching the log file, just in case you are able to spot something. > > > > I think config.log is more helpful, as it would show LDFLAGS and detected > > threading library. > > Hi Mel, > > There sure is plenty in config.log to interest you. Attached is the log > in zip format. No mention of -llthread there. It links so I'm assuming you have devel/linuxthreads installed. Could you show: make -C /usr/ports/lang/guild -V CONFIGURE_ENV -V CONFIGURE_ARGS It must come from somewhere...Your environment and /etc/make.conf are free from LDFLAGS or LIBS according to config.log. > Could you please clear up one question : do the freebsd-question forum > rules allow attachments ? I am actually using 'Reply to sender' rather > than 'Reply to all' because of this doubt. On -questions attachments are stripped to the best of my knowledge. -- Mel ___ 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: guile-1.8.6 build core dumps (autoconf issue ?)
On Tuesday 31 March 2009 19:02:56 manish jain wrote: > Mel Flynn wrote: > > On Tuesday 31 March 2009 08:15:56 manish jain wrote: > >> Hi, > >> > >> I portsnapped the lastest tarball a couple of days back. Doing a build > >> > >> in lang/guile (1.8.6) core dumps with the following message : > >>> Making all in libguile > >>> gmake[2]: Entering directory > >>> `/usr/ports/lang/guile/work/guile-1.8.6/libguile' cd .. && /bin/sh > >>> ./config.status libguile/Makefile depfiles > >>> config.status: creating libguile/Makefile > >>> config.status: executing depfiles commands > >>> gmake[2]: Leaving directory > >>> `/usr/ports/lang/guile/work/guile-1.8.6/libguile' gmake[2]: Entering > >>> directory `/usr/ports/lang/guile/work/guile-1.8.6/libguile' Generating > >>> libpath.h... > >>> sed < ./version.h.in > version.h.tmp \ > >>> -e s:@-GUILE_MAJOR_VERSION-@:1: \ > >>> -e s:@-GUILE_MINOR_VERSION-@:8: \ > >>> -e s:@-GUILE_MICRO_VERSION-@:6: > >>> mv version.h.tmp version.h > >>> if [ "no" = "yes" ]; then \ > >>> cc -DHAVE_CONFIG_H -I.. -I.. -I.. -c -o gen-scmconfig.o > >>> gen-scmconfig.c; \ else \ > >>> cc -DHAVE_CONFIG_H -I.. -I.. -I.. -I/usr/local/include -O2 > >>> -fno-strict-aliasing -pipe -Wall -Wmissing-prototypes -Werror -c -o > >>> gen-scmconfig.o gen-scmconfig.c; \ fi > >>> if [ "no" = "yes" ]; then \ > >>> cc -o gen-scmconfig gen-scmconfig.o; \ > >>> else \ > >>> /bin/sh ../libtool --tag=CC --mode=link cc -O2 > >>> -fno-strict-aliasing -pipe -Wall -Wmissing-prototypes -Werror > >>> -L/usr/local/lib -o > >>> gen-scmconfig gen-scmconfig.o -llthread -lgmp -lcrypt -lm -lltdl ; \ > >>> fi libtool: link: cc -O2 -fno-strict-aliasing -pipe -Wall > >>> -Wmissing-prototypes -Werror -o gen-scmconfig gen-scmconfig.o > >>> -L/usr/local/lib -llthread /usr/local/lib/libgmp.so -lcrypt -lm > > > > vs mine: > > libtool: link: /usr/local/libexec/ccache/world-cc -O2 > > -fno-strict-aliasing - pipe -Wall -Wmissing-prototypes -Werror -o > > gen-scmconfig gen-scmconfig.o - L/usr/local/lib /usr/local/lib/libgmp.so > > -lcrypt -lm /usr/local/lib/libltdl.so -Wl,-rpath -Wl,/usr/local/lib > > -Wl,-rpath -Wl,/usr/local/lib > > > > Where does -llthread come from? > > Hi Mel, > > I can't really answer the question. I just ran 'make install clean'. I > am attaching the log file, just in case you are able to spot something. I think config.log is more helpful, as it would show LDFLAGS and detected threading library. -- Mel ___ 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: guile-1.8.6 build core dumps (autoconf issue ?)
On Tuesday 31 March 2009 08:15:56 manish jain wrote: > Hi, > > I portsnapped the lastest tarball a couple of days back. Doing a build > > in lang/guile (1.8.6) core dumps with the following message : > > Making all in libguile > > gmake[2]: Entering directory > > `/usr/ports/lang/guile/work/guile-1.8.6/libguile' cd .. && /bin/sh > > ./config.status libguile/Makefile depfiles > > config.status: creating libguile/Makefile > > config.status: executing depfiles commands > > gmake[2]: Leaving directory > > `/usr/ports/lang/guile/work/guile-1.8.6/libguile' gmake[2]: Entering > > directory `/usr/ports/lang/guile/work/guile-1.8.6/libguile' Generating > > libpath.h... > > sed < ./version.h.in > version.h.tmp \ > > -e s:@-GUILE_MAJOR_VERSION-@:1: \ > > -e s:@-GUILE_MINOR_VERSION-@:8: \ > > -e s:@-GUILE_MICRO_VERSION-@:6: > > mv version.h.tmp version.h > > if [ "no" = "yes" ]; then \ > > cc -DHAVE_CONFIG_H -I.. -I.. -I.. -c -o gen-scmconfig.o > > gen-scmconfig.c; \ else \ > > cc -DHAVE_CONFIG_H -I.. -I.. -I.. -I/usr/local/include -O2 > > -fno-strict-aliasing -pipe -Wall -Wmissing-prototypes -Werror -c -o > > gen-scmconfig.o gen-scmconfig.c; \ fi > > if [ "no" = "yes" ]; then \ > > cc -o gen-scmconfig gen-scmconfig.o; \ > > else \ > > /bin/sh ../libtool --tag=CC --mode=link cc -O2 > > -fno-strict-aliasing > > -pipe -Wall -Wmissing-prototypes -Werror -L/usr/local/lib -o > > gen-scmconfig gen-scmconfig.o -llthread -lgmp -lcrypt -lm -lltdl ; \ fi > > libtool: link: cc -O2 -fno-strict-aliasing -pipe -Wall > > -Wmissing-prototypes -Werror -o gen-scmconfig gen-scmconfig.o > > -L/usr/local/lib -llthread /usr/local/lib/libgmp.so -lcrypt -lm vs mine: libtool: link: /usr/local/libexec/ccache/world-cc -O2 -fno-strict-aliasing - pipe -Wall -Wmissing-prototypes -Werror -o gen-scmconfig gen-scmconfig.o - L/usr/local/lib /usr/local/lib/libgmp.so -lcrypt -lm /usr/local/lib/libltdl.so -Wl,-rpath -Wl,/usr/local/lib -Wl,-rpath -Wl,/usr/local/lib Where does -llthread come from? -- Mel ___ 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"
guile-1.8.6 build core dumps (autoconf issue ?)
Hi, I portsnapped the lastest tarball a couple of days back. Doing a build in lang/guile (1.8.6) core dumps with the following message : Making all in libguile gmake[2]: Entering directory `/usr/ports/lang/guile/work/guile-1.8.6/libguile' cd .. && /bin/sh ./config.status libguile/Makefile depfiles config.status: creating libguile/Makefile config.status: executing depfiles commands gmake[2]: Leaving directory `/usr/ports/lang/guile/work/guile-1.8.6/libguile' gmake[2]: Entering directory `/usr/ports/lang/guile/work/guile-1.8.6/libguile' Generating libpath.h... sed < ./version.h.in > version.h.tmp \ -e s:@-GUILE_MAJOR_VERSION-@:1: \ -e s:@-GUILE_MINOR_VERSION-@:8: \ -e s:@-GUILE_MICRO_VERSION-@:6: mv version.h.tmp version.h if [ "no" = "yes" ]; then \ cc -DHAVE_CONFIG_H -I.. -I.. -I.. -c -o gen-scmconfig.o gen-scmconfig.c; \ else \ cc -DHAVE_CONFIG_H -I.. -I.. -I.. -I/usr/local/include -O2 -fno-strict-aliasing -pipe -Wall -Wmissing-prototypes -Werror -c -o gen-scmconfig.o gen-scmconfig.c; \ fi if [ "no" = "yes" ]; then \ cc -o gen-scmconfig gen-scmconfig.o; \ else \ /bin/sh ../libtool --tag=CC --mode=link cc -O2 -fno-strict-aliasing -pipe -Wall -Wmissing-prototypes -Werror -L/usr/local/lib -o gen-scmconfig gen-scmconfig.o -llthread -lgmp -lcrypt -lm -lltdl ; \ fi libtool: link: cc -O2 -fno-strict-aliasing -pipe -Wall -Wmissing-prototypes -Werror -o gen-scmconfig gen-scmconfig.o -L/usr/local/lib -llthread /usr/local/lib/libgmp.so -lcrypt -lm /usr/local/lib/libltdl.so -Wl,-rpath -Wl,/usr/local/lib -Wl,-rpath -Wl,/usr/local/lib rm -f scmconfig.h.tmp cat ./scmconfig.h.top > scmconfig.h.tmp ./gen-scmconfig >> scmconfig.h.tmp Segmentation fault (core dumped) gmake[2]: *** [scmconfig.h] Error 139 gmake[2]: Leaving directory `/usr/ports/lang/guile/work/guile-1.8.6/libguile' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/lang/guile/work/guile-1.8.6' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/lang/guile. The complete logfile is more than 27 kb, which anybody can get from me by sending me a separate mail. One point of interest in the previous sections of the build states that guile-1.8.6 is to be configured with autoconf-2.63 whereas the latest autoconf port available is 2.62. -- Thank you and Regards Manish Jain invalid.poin...@gmail.com +91-99830-62246 NB : Laast year I kudn't spell Software Engineer. Now I are won. ___ 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"
FreeBSD 7.1-STABLE/amd64: pkg_delete core dumps
Since several weeks now /usr/sbin/pkg_delete core dumps whenever I try to delete an obsolete package or portupgrade tries to do so. The box is a Quad Core most recent FreeBSD 7.1-STABLE box as built world of today's sources. Regards, Oliver ___ 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: analyzing freebsd core dumps
On Wed, Oct 08, 2008 at 08:30:12AM +0200, Mister Olli wrote: > hi... > > thanks for the feedback on this topic. > the first step to clean the machine and check all connectors has been > done yesterday. I hope that this will fix the problem, and that it's not > some kind of hardware failure. > > to run tests with memtest is quite a problem, since the machine has high > availability requirements. to take it off for nearly one hour for > cleaning and checking during daily work of our company was a pain. > 6 hours or more of RAM tests is not possible. > > is there some other way to detect hardware failure with less time > consuming tool/ process? Yes -- you start replacing hardware one piece at a time until the problem goes away. That will also require downtime, quite regularly, and waste money. So to answer your question: no, there is no way to easily track down the source of a hardware failure, or determine what piece has failed (if any). This is completely 100% normal when it comes to computers, especially x86 PCs. Anyone who has worked in the IT field for many years knows this. :-) I'm amazed that in this day and age, any company would have a single host as a single-point-of-failure. You can't take this machine down for troubleshooting, but you have no failover available. The company has put themselves into this situation. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: analyzing freebsd core dumps
hi... thanks for the feedback on this topic. the first step to clean the machine and check all connectors has been done yesterday. I hope that this will fix the problem, and that it's not some kind of hardware failure. to run tests with memtest is quite a problem, since the machine has high availability requirements. to take it off for nearly one hour for cleaning and checking during daily work of our company was a pain. 6 hours or more of RAM tests is not possible. is there some other way to detect hardware failure with less time consuming tool/ process? greetz olli Am Montag, den 06.10.2008, 13:45 -0400 schrieb Jerry McAllister: > On Mon, Oct 06, 2008 at 10:18:09AM -0700, Jeremy Chadwick wrote: > > > On Mon, Oct 06, 2008 at 08:04:07AM +0200, Mister Olli wrote: > > > hi list... > > > > > > I have a freebsd maschine running for more 6 months without any > > > problems. > > > the machine's only service is to be an openvpn gateway for a hand of > > > users. > > > > > > 2 weeks ago the first problems started. the openvpn exited with signal > > > 11 and 4 and core dumps were written. > > > > > > the same happend yesterday with the postfix/cleanup process, and the > > > suddenly the machine rebooted without any further log messages. > > > > > > what is the best way to troubleshoot the cause of this problem? > > > > Signal 11 happening "out of no where" on machines which have been > > running fine, most of the time, is a sign of hardware failure (usually > > RAM, but sometimes motherboard or PSU). The fact you got a reboot is > > also further evidence of this. > > > > http://www.freebsd.org/doc/en/books/faq/troubleshoot.html#SIGNAL11 > > > > I would recommend taking the machine offline and running something like > > memtest86+ on it for 6-7 hours. Any errors seen are a pretty good sign > > that you should replace the memory or the motherboard. You can > > download an ISO or floppy disk images here: > > > > http://www.memtest.org/ > > > > Bottom line is that this is probably a hardware issue. > > Could also be a contacts if it is not the actual memory or board. > A marginal contact where something is plugged in can over time > build up deposits that make it fail. Of course, this is still > a hardware problem, but can often be cured by reseating everything. > If it is bad enough, it could also be exacerbated by reseating > everything. > > jerry > > > > > -- > > | Jeremy Chadwickjdc at parodius.com | > > | Parodius Networking http://www.parodius.com/ | > > | UNIX Systems Administrator Mountain View, CA, USA | > > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > > > ___ > > 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: analyzing freebsd core dumps
On Mon, Oct 06, 2008 at 10:18:09AM -0700, Jeremy Chadwick wrote: > On Mon, Oct 06, 2008 at 08:04:07AM +0200, Mister Olli wrote: > > hi list... > > > > I have a freebsd maschine running for more 6 months without any > > problems. > > the machine's only service is to be an openvpn gateway for a hand of > > users. > > > > 2 weeks ago the first problems started. the openvpn exited with signal > > 11 and 4 and core dumps were written. > > > > the same happend yesterday with the postfix/cleanup process, and the > > suddenly the machine rebooted without any further log messages. > > > > what is the best way to troubleshoot the cause of this problem? > > Signal 11 happening "out of no where" on machines which have been > running fine, most of the time, is a sign of hardware failure (usually > RAM, but sometimes motherboard or PSU). The fact you got a reboot is > also further evidence of this. > > http://www.freebsd.org/doc/en/books/faq/troubleshoot.html#SIGNAL11 > > I would recommend taking the machine offline and running something like > memtest86+ on it for 6-7 hours. Any errors seen are a pretty good sign > that you should replace the memory or the motherboard. You can > download an ISO or floppy disk images here: > > http://www.memtest.org/ > > Bottom line is that this is probably a hardware issue. Could also be a contacts if it is not the actual memory or board. A marginal contact where something is plugged in can over time build up deposits that make it fail. Of course, this is still a hardware problem, but can often be cured by reseating everything. If it is bad enough, it could also be exacerbated by reseating everything. jerry > > -- > | Jeremy Chadwickjdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > ___ > 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: analyzing freebsd core dumps
On Mon, Oct 06, 2008 at 08:04:07AM +0200, Mister Olli wrote: > hi list... > > I have a freebsd maschine running for more 6 months without any > problems. > the machine's only service is to be an openvpn gateway for a hand of > users. > > 2 weeks ago the first problems started. the openvpn exited with signal > 11 and 4 and core dumps were written. > > the same happend yesterday with the postfix/cleanup process, and the > suddenly the machine rebooted without any further log messages. > > what is the best way to troubleshoot the cause of this problem? Signal 11 happening "out of no where" on machines which have been running fine, most of the time, is a sign of hardware failure (usually RAM, but sometimes motherboard or PSU). The fact you got a reboot is also further evidence of this. http://www.freebsd.org/doc/en/books/faq/troubleshoot.html#SIGNAL11 I would recommend taking the machine offline and running something like memtest86+ on it for 6-7 hours. Any errors seen are a pretty good sign that you should replace the memory or the motherboard. You can download an ISO or floppy disk images here: http://www.memtest.org/ Bottom line is that this is probably a hardware issue. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
analyzing freebsd core dumps
hi list... I have a freebsd maschine running for more 6 months without any problems. the machine's only service is to be an openvpn gateway for a hand of users. 2 weeks ago the first problems started. the openvpn exited with signal 11 and 4 and core dumps were written. the same happend yesterday with the postfix/cleanup process, and the suddenly the machine rebooted without any further log messages. what is the best way to troubleshoot the cause of this problem? greetz olli ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: python25 core dumps
On Thursday 15 November 2007 03:07:03 am Heiko Wundram (Beenic) wrote: > This seems like a problem in qt4 (I don't think the problem is in PyQt), > simply try reinstalling that, too (completely; qt4 is split into several > ports and "pkg_info | grep qt4" is your friend here). A complete rebuild of qt4-* did not solve the problem, however, a complete rebuild of py25-qt4* solved everything. (Except the Gtk problems, naturally) Apparently there was something in the pre-built packages that didn't agree with my machine. I'm hoping that a rebuild of all dependencies for gramps will solve the problems there as well. David -- If this message was not entertaining, write your congressman. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: python25 core dumps
On Thursday 15 November 2007 03:07:03 am Heiko Wundram (Beenic) wrote: > This seems like a problem in libaspell; maybe you should simply try to > reinstall the aspell port. See below for more info. I rebuilt aspell, but gramps still core dumps. The backtrace shows the same as previously. :/ > > For comparison, this is what a crash from eric4 (built with PyQt4) looks > > like: > This seems like a problem in qt4 (I don't think the problem is in PyQt), > simply try reinstalling that, too (completely; qt4 is split into several > ports and "pkg_info | grep qt4" is your friend here). > > Generally, from what I interpret into the second backtrace, you upgraded > from some 6 release to 7.0-BETA2, which (amongst other things) means that > the C++ libraries have changed (because of a newer compiler, gcc 3.3 vs. > 4.2). The compiler has also had changes introduced to the C++ type info > descriptor layout (which I should think causes the segmentation fault in > typeinfo name in the second backtrace), so that if you have a program > that's linked against different versions of libstdc++ (PyQt is linked > against that, just as qt4 is), you'll see behaviour like this. > > To check whether my hypothesis is correct, simply do an ldd on both a PyQt > library, and a qt4 shared library (locations of both of which you can > extract from the backtrace). If the version of libstdc++ is different, you > didn't follow the upgrading procedure which explicitly states to recompile > _all_ ports for the new system. These appear to be the same, but its possible my blurry eyes may be overlooking something obvious. /usr/local/lib/libQtGui.so.4: libpng.so.5 => /usr/local/lib/libpng.so.5 (0x28185000) libSM.so.6 => /usr/local/lib/libSM.so.6 (0x281aa000) libICE.so.6 => /usr/local/lib/libICE.so.6 (0x281b2000) libQtCore.so.4 => /usr/local/lib/libQtCore.so.4 (0x28a1a000) libz.so.4 => /lib/libz.so.4 (0x281c9000) libgthread-2.0.so.0 => /usr/local/lib/libgthread-2.0.so.0 (0x281db000) libglib-2.0.so.0 => /usr/local/lib/libglib-2.0.so.0 (0x28b89000) libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x28c27000) libXi.so.6 => /usr/local/lib/libXi.so.6 (0x281e) libXrender.so.1 => /usr/local/lib/libXrender.so.1 (0x281e8000) libXrandr.so.2 => /usr/local/lib/libXrandr.so.2 (0x281f) libXfixes.so.3 => /usr/local/lib/libXfixes.so.3 (0x281f7000) libXcursor.so.1 => /usr/local/lib/libXcursor.so.1 (0x28d1c000) libXinerama.so.1 => /usr/local/lib/libXinerama.so.1 (0x281fc000) libfreetype.so.9 => /usr/local/lib/libfreetype.so.9 (0x28d25000) libfontconfig.so.1 => /usr/local/lib/libfontconfig.so.1 (0x28d93000) libXext.so.6 => /usr/local/lib/libXext.so.6 (0x28dbd000) libX11.so.6 => /usr/local/lib/libX11.so.6 (0x28dcb000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x28eb8000) libm.so.5 => /lib/libm.so.5 (0x28fa2000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x28fb7000) libthr.so.3 => /lib/libthr.so.3 (0x28fc2000) libc.so.7 => /lib/libc.so.7 (0x28089000) libintl.so.8 => /usr/local/lib/libintl.so.8 (0x28fd4000) libpcre.so.0 => /usr/local/lib/libpcre.so.0 (0x28fdd000) libexpat.so.6 => /usr/local/lib/libexpat.so.6 (0x29003000) libXau.so.6 => /usr/local/lib/libXau.so.6 (0x29023000) libXdmcp.so.6 => /usr/local/lib/libXdmcp.so.6 (0x29026000) librpcsvc.so.4 => /usr/lib/librpcsvc.so.4 (0x2902b000) /usr/local/lib/python2.5/site-packages/PyQt4/QtGui.so: libQtGui.so.4 => /usr/local/lib/libQtGui.so.4 (0x28b09000) libpng.so.5 => /usr/local/lib/libpng.so.5 (0x28185000) libSM.so.6 => /usr/local/lib/libSM.so.6 (0x281aa000) libICE.so.6 => /usr/local/lib/libICE.so.6 (0x281b2000) libQtCore.so.4 => /usr/local/lib/libQtCore.so.4 (0x29223000) libz.so.4 => /lib/libz.so.4 (0x281c9000) libgthread-2.0.so.0 => /usr/local/lib/libgthread-2.0.so.0 (0x281db000) libglib-2.0.so.0 => /usr/local/lib/libglib-2.0.so.0 (0x29392000) libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x2943) libXi.so.6 => /usr/local/lib/libXi.so.6 (0x281e) libXrender.so.1 => /usr/local/lib/libXrender.so.1 (0x281e8000) libXrandr.so.2 => /usr/local/lib/libXrandr.so.2 (0x281f) libXfixes.so.3 => /usr/local/lib/libXfixes.so.3 (0x281f7000) libXcursor.so.1 => /usr/local/lib/libXcursor.so.1 (0x29525000) libXinerama.so.1 => /usr/local/lib/libXinerama.so.1 (0x281fc000) libfreetype.so.9 => /usr/local/lib/libfreetype.so.9 (0x2952e000) libfontconfig.so.1 => /usr/local/lib/libfontconfig.so.1 (0x2959c000) libXext.so.
Re: python25 core dumps
Am Donnerstag, 15. November 2007 04:07:26 schrieb David J Brooks: > Ok. Here's what gdb shows for a crash from Gramps (built with py-Gtk2): > > (gdb) back > #0 0x29ea37fd in delete_aspell_speller () from > /usr/local/lib/libaspell.so.16 #1 0x29e03b3d in > gtkspell_set_language_internal () > from /usr/local/lib/libgtkspell.so.0 > #2 0x29e04084 in gtkspell_set_language () > from /usr/local/lib/libgtkspell.so.0 > #3 0x29af90ae in ?? () > from /usr/local/lib/python2.5/site-packages/gtk-2.0/gtkspell.so > #4 0x29cdf180 in ?? () > #5 0x29d28ff4 in ?? () > #6 0x in ?? () > #7 0xbfbf5218 in ?? () > #8 0xbfbf5220 in ?? () > #9 0x29d284cc in ?? () > #10 0x29af9681 in ?? () > from /usr/local/lib/python2.5/site-packages/gtk-2.0/gtkspell.so > #11 0x in ?? () > #12 0x29d28ff4 in ?? () > #13 0x28308080 in ?? () > #14 0xbfbf53c8 in ?? () > #15 0x080b131a in PyEval_EvalFrameEx () > Previous frame identical to this frame (corrupt stack?) > (gdb) This seems like a problem in libaspell; maybe you should simply try to reinstall the aspell port. See below for more info. > For comparison, this is what a crash from eric4 (built with PyQt4) looks > like: > > (gdb) back > #0 0x29224448 in typeinfo name for sipQApplication () >from /usr/local/lib/python2.5/site-packages/PyQt4/QtGui.so > #1 0x29595531 in sm_performSaveYourself () from > /usr/local/lib/libQtGui.so.4 #2 0x295956a1 in sm_saveYourselfCallback () > from /usr/local/lib/libQtGui.so.4 #3 0x29aed10b in _SmcProcessMessage () > from /usr/local/lib/libSM.so.6 #4 0x29afffa3 in IceProcessMessages () from > /usr/local/lib/libICE.so.6 #5 0x2958f5c8 in > QSmSocketReceiver::socketActivated () > from /usr/local/lib/libQtGui.so.4 > #6 0x2958f62f in QSmSocketReceiver::qt_metacall () > from /usr/local/lib/libQtGui.so.4 > #7 0x287bc15f in QMetaObject::activate () from > /usr/local/lib/libQtCore.so.4 #8 0x287bc6d2 in QMetaObject::activate () > from /usr/local/lib/libQtCore.so.4 #9 0x287d8b33 in > QSocketNotifier::activated () > from /usr/local/lib/libQtCore.so.4 > #10 0x287c1e1f in QSocketNotifier::event () from > /usr/local/lib/libQtCore.so.4 #11 0x295467bd in > QApplicationPrivate::notify_helper () > from /usr/local/lib/libQtGui.so.4 > #12 0x2954c8fe in QApplication::notify () from /usr/local/lib/libQtGui.so.4 > #13 0x291b4a13 in sipQApplication::notify () > from /usr/local/lib/python2.5/site-packages/PyQt4/QtGui.so > #14 0x287ab07b in QCoreApplication::notifyInternal () > from /usr/local/lib/libQtCore.so.4 > #15 0x287ccaf3 in socketNotifierSourceDispatch () > from /usr/local/lib/libQtCore.so.4 > #16 0x28852886 in g_main_context_dispatch () > from /usr/local/lib/libglib-2.0.so.0 > #17 0x28855c02 in g_main_context_check () from > /usr/local/lib/libglib-2.0.so.0 #18 0x28856185 in g_main_context_iteration > () > from /usr/local/lib/libglib-2.0.so.0 > #19 0x287ccf78 in QEventDispatcherGlib::processEvents () > from /usr/local/lib/libQtCore.so.4 > #20 0x295bd965 in QGuiEventDispatcherGlib::processEvents () > from /usr/local/lib/libQtGui.so.4 > #21 0x287aac31 in QCoreApplication::processEvents () > from /usr/local/lib/libQtCore.so.4 > #22 0x28623966 in meth_QCoreApplication_processEvents () >from /usr/local/lib/python2.5/site-packages/PyQt4/QtCore.so > #23 0x080b131a in PyEval_EvalFrameEx () > #24 0x080b1fab in PyEval_EvalFrameEx () > #25 0x080b1fab in PyEval_EvalFrameEx () > #26 0x080b2919 in PyEval_EvalCodeEx () > #27 0x080b2a67 in PyEval_EvalCode () > #28 0x080c9fc6 in Py_CompileString () > #29 0x080ca070 in PyRun_FileExFlags () > #30 0x080cb569 in PyRun_SimpleFileExFlags () > #31 0x08056ef1 in Py_Main () > #32 0x080563b5 in main () > (gdb) This seems like a problem in qt4 (I don't think the problem is in PyQt), simply try reinstalling that, too (completely; qt4 is split into several ports and "pkg_info | grep qt4" is your friend here). Generally, from what I interpret into the second backtrace, you upgraded from some 6 release to 7.0-BETA2, which (amongst other things) means that the C++ libraries have changed (because of a newer compiler, gcc 3.3 vs. 4.2). The compiler has also had changes introduced to the C++ type info descriptor layout (which I should think causes the segmentation fault in typeinfo name in the second backtrace), so that if you have a program that's linked against different versions of libstdc++ (PyQt is linked against that, just as qt4 is), you'll see behaviour like this. To check whether my hypothesis is correct, simply do an ldd on both a PyQt library, and a qt4 shared library (locations of both of which you can extract from the backtrace). If the version of libstdc++ is different, you didn't follow the upgrading procedure which explicitly states to recompile _all_ ports for the new system. Output should look something like this, anyway: [EMAIL PROTECTED] ~]$ ldd /usr/local/lib/libqt-mt.so.3 /usr/local/lib/libqt-mt.so.3: ... libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x28c4c000) ... [EMAIL PROTECTE
Re: python25 core dumps
On Wednesday 14 November 2007 05:57:52 pm Heiko Wundram (Beenic) wrote: > Am Mittwoch, 14. November 2007 23:15:36 schrieb David J Brooks: > > Since upgrading to 7.0-BETA2 most of my python based programs fail with > > Segmentation fault: 11 (core dumped). It seems to be limited to gui based > > programs using Gtk or Qt. Any idea what's going on there? Hints on how to > > analyze the python.core files would be helpful too. > > Easy way to get info from the backtrace: > > gdb /usr/local/bin/python /python.core > > Then, enter the "back" command in the post-mortem debugging session and > post the output here. Someone (maybe even me) should be able to give you a > hint where to look further from there. Ok. Here's what gdb shows for a crash from Gramps (built with py-Gtk2): (gdb) back #0 0x29ea37fd in delete_aspell_speller () from /usr/local/lib/libaspell.so.16 #1 0x29e03b3d in gtkspell_set_language_internal () from /usr/local/lib/libgtkspell.so.0 #2 0x29e04084 in gtkspell_set_language () from /usr/local/lib/libgtkspell.so.0 #3 0x29af90ae in ?? () from /usr/local/lib/python2.5/site-packages/gtk-2.0/gtkspell.so #4 0x29cdf180 in ?? () #5 0x29d28ff4 in ?? () #6 0x in ?? () #7 0xbfbf5218 in ?? () #8 0xbfbf5220 in ?? () #9 0x29d284cc in ?? () #10 0x29af9681 in ?? () from /usr/local/lib/python2.5/site-packages/gtk-2.0/gtkspell.so #11 0x in ?? () #12 0x29d28ff4 in ?? () #13 0x28308080 in ?? () #14 0xbfbf53c8 in ?? () #15 0x080b131a in PyEval_EvalFrameEx () Previous frame identical to this frame (corrupt stack?) (gdb) For comparison, this is what a crash from eric4 (built with PyQt4) looks like: (gdb) back #0 0x29224448 in typeinfo name for sipQApplication () from /usr/local/lib/python2.5/site-packages/PyQt4/QtGui.so #1 0x29595531 in sm_performSaveYourself () from /usr/local/lib/libQtGui.so.4 #2 0x295956a1 in sm_saveYourselfCallback () from /usr/local/lib/libQtGui.so.4 #3 0x29aed10b in _SmcProcessMessage () from /usr/local/lib/libSM.so.6 #4 0x29afffa3 in IceProcessMessages () from /usr/local/lib/libICE.so.6 #5 0x2958f5c8 in QSmSocketReceiver::socketActivated () from /usr/local/lib/libQtGui.so.4 #6 0x2958f62f in QSmSocketReceiver::qt_metacall () from /usr/local/lib/libQtGui.so.4 #7 0x287bc15f in QMetaObject::activate () from /usr/local/lib/libQtCore.so.4 #8 0x287bc6d2 in QMetaObject::activate () from /usr/local/lib/libQtCore.so.4 #9 0x287d8b33 in QSocketNotifier::activated () from /usr/local/lib/libQtCore.so.4 #10 0x287c1e1f in QSocketNotifier::event () from /usr/local/lib/libQtCore.so.4 #11 0x295467bd in QApplicationPrivate::notify_helper () from /usr/local/lib/libQtGui.so.4 #12 0x2954c8fe in QApplication::notify () from /usr/local/lib/libQtGui.so.4 #13 0x291b4a13 in sipQApplication::notify () from /usr/local/lib/python2.5/site-packages/PyQt4/QtGui.so #14 0x287ab07b in QCoreApplication::notifyInternal () from /usr/local/lib/libQtCore.so.4 #15 0x287ccaf3 in socketNotifierSourceDispatch () from /usr/local/lib/libQtCore.so.4 #16 0x28852886 in g_main_context_dispatch () from /usr/local/lib/libglib-2.0.so.0 #17 0x28855c02 in g_main_context_check () from /usr/local/lib/libglib-2.0.so.0 #18 0x28856185 in g_main_context_iteration () from /usr/local/lib/libglib-2.0.so.0 #19 0x287ccf78 in QEventDispatcherGlib::processEvents () from /usr/local/lib/libQtCore.so.4 #20 0x295bd965 in QGuiEventDispatcherGlib::processEvents () from /usr/local/lib/libQtGui.so.4 #21 0x287aac31 in QCoreApplication::processEvents () from /usr/local/lib/libQtCore.so.4 #22 0x28623966 in meth_QCoreApplication_processEvents () from /usr/local/lib/python2.5/site-packages/PyQt4/QtCore.so #23 0x080b131a in PyEval_EvalFrameEx () #24 0x080b1fab in PyEval_EvalFrameEx () #25 0x080b1fab in PyEval_EvalFrameEx () #26 0x080b2919 in PyEval_EvalCodeEx () #27 0x080b2a67 in PyEval_EvalCode () #28 0x080c9fc6 in Py_CompileString () #29 0x080ca070 in PyRun_FileExFlags () #30 0x080cb569 in PyRun_SimpleFileExFlags () #31 0x08056ef1 in Py_Main () #32 0x080563b5 in main () (gdb) I tried tovidgui (build with Tkinter) and it did not crash. David -- Federal law prohibits deleting this message. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: python25 core dumps
On Thu, 15 Nov 2007 00:57:52 +0100
"Heiko Wundram (Beenic)" <[EMAIL PROTECTED]> wrote:
> Am Mittwoch, 14. November 2007 23:15:36 schrieb David J Brooks:
> > Since upgrading to 7.0-BETA2 most of my python based programs fail with
> > Segmentation fault: 11 (core dumped). It seems to be limited to gui based
> > programs using Gtk or Qt. Any idea what's going on there? Hints on how to
> > analyze the python.core files would be helpful too.
>
> Easy way to get info from the backtrace:
>
> gdb /usr/local/bin/python /python.core
>
> Then, enter the "back" command in the post-mortem debugging session and post
> the output here. Someone (maybe even me) should be able to give you a hint
> where to look further from there.
same happens here with castpodder (which is a gtk/python tool), but i havent
been able to find a .core . I need to look into a ktrace and step into the code
with pydev in eclipse.
B
_
{Beto|Norberto|Numard} Meijome
You shouldn't verb words.
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: python25 core dumps
Am Mittwoch, 14. November 2007 23:15:36 schrieb David J Brooks: > Since upgrading to 7.0-BETA2 most of my python based programs fail with > Segmentation fault: 11 (core dumped). It seems to be limited to gui based > programs using Gtk or Qt. Any idea what's going on there? Hints on how to > analyze the python.core files would be helpful too. Easy way to get info from the backtrace: gdb /usr/local/bin/python /python.core Then, enter the "back" command in the post-mortem debugging session and post the output here. Someone (maybe even me) should be able to give you a hint where to look further from there. -- Heiko Wundram Product & Application Development ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
python25 core dumps
Since upgrading to 7.0-BETA2 most of my python based programs fail with Segmentation fault: 11 (core dumped). It seems to be limited to gui based programs using Gtk or Qt. Any idea what's going on there? Hints on how to analyze the python.core files would be helpful too. David -- This message coming soon to an illegal DVD. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Lack of Core Dumps on signal 11
FreeBSD 6.2-RELEASE-p4 The setup I have used for earlier versions to obtain core dumps on processes that receive signals is no longer working. /var/log/ messages no longer shows core dumped for the entries and nothing appears in the core dump directory. sysctl.conf has: kern.sugid_coredump=1 kern.corefile=/usr/var/crash/%N.core /usr/var/crash has permissions of 777. There are no symlinks in the path. Symlinks didn't work in earlier versions. I need to keep all the core dumps in one directory so they can be found easily. Otherwise they end up all over the place and are qutie difficult to find. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Selecting printer from apps core dumps. Howto debug?
On Sat, Jun 30, 2007, at 22:06:58 +0100, Graham Bentley wrote: > Its odd because the cups test page works, printing from > mousepad and firefox works, but abiword bombs completely. > In the short space of time I see it on the screen after > clicking print I can see there is no entry for the printer. [...] > [SOLVED] Set printer as 'default' using cups webmin. > > All working - thanks :) Sorry to bring back the thread but I'm seeing this issue with a fresh install of everything on a new machine. Printing to an Epson USB printer from the CUPS test page works fine, as does printing from Opera using the lpr binary installed by CUPS. When trying to print via AbiWord or Claws Mail, they coredump. If the printer is not set as default in CUPS (which is how I had it set before reading this thread), it does bring up the print dialog in Abiword/Claws but it dumps when you select the printer. If the printer is set as default in CUPS, the app dumps right when opening the print dialog and before the printer even shows up on the list of available printers. I think it's a somewhat new problem somewhere because I've been using Xfce, CUPS, and these applications for quite a while on other machines with no problems. CUPS is enabled in xfce4-print as well as libgnomeprint, and GNOME printing is enabled in Claws Mail. The USB permissions are also set properly. I also tried running AbiWord outside of Xfce (in Xorg's default WM) which did the same thing. Maybe it's something with libgnomeprint since both apps use it and both have problems printing? Here is a list of relevant software versions on the non working machine: abiword-2.4.6_1 claws-mail-2.10.0 cups-base-1.2.11_2 cups-pstoraster-8.15.4_1 gutenprint-cups-5.1.3 libgnomecups-0.2.2_4,1 libgnomeprint-2.18.0_2 libgnomeprintui-2.18.0_1 xfce4-print-4.4.1_1 Here is a list of relevant software versions on a machine that is printing properly with Claws-Mail (and probably would with AbiWord if it didn't have a problem with some laser printers): abiword-gnome-2.4.6 claws-mail-2.8.1 cups-base-1.2.8 libgnomecups-0.2.2_2,1 libgnomeprint-2.12.1_3 libgnomeprintui-2.12.1_2 xfce4-print-4.4.0 Here's the backtrace from AbiWord if it helps: http://tntpowerhost.com/mixx941/gdb_abiword_print.txt Please let me know if I can provide any additional info. Thanks in advance for any suggestions on how to fix or debug this. -Mark -- Internet Radio: Party107 (Trance/Electronic) - http://www.party107.com Rock 101.9 The Edge (Rock) - http://www.rock1019.net IRC: MIXXnet IRC Network - irc.mixxnet.net (Nick: MIXX941) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Selecting printer from apps core dumps. Howto debug?
(I proposed you a couple of things but generally it's a good idea to ask this on freebsd-gnome@ as well, since at least the Abiword problem is _maybe_ related to libgnomeprintui <-> Xfce.) On Sat, 30 Jun 2007 22:06:58 +0100 Graham Bentley <[EMAIL PROTECTED]> wrote: > > have you compiled print/xfce4-print with "Use cups as > > printing system"? This matters, among other things. You > > can check it with 'make showconfig' and change with > > 'make config'. > > 3bsd# make showconfig > ===> The following configuration options are available for > xfce4-print-4.4.1_1: LPR=off "Use lpr as printing system" > CUPS=on "Use cups as printing system" > LETTER=off "Use letter paper format instead of A4" > ===> Use 'make config' to modify these settings > 3bsd# Ok... > Its odd because the cups test page works, printing from > mousepad and firefox works, but abiword bombs completely. > In the short space of time I see it on the screen after > clicking print I can see there is no entry for the printer. AFAIK Abiword has known (and very old) problem with Xfce, mainly reflected in printing. As far as I understand it (I use neither Abiword nor CUPS) the cause could be the Abiword's (false) expectations of pure GNOME environment (including printing), which is only partially true in Xfce. You can try this, but I have no idea what can happen: # portupgrade -f -m 'WANT_GNOME=no' abiword Besides that, Claws Mail has by default similar expectations regarding printing (libgnomeprintui). Do you have printing problems in Claws Mail? Can you post here 'make showconfig" of mail/claws-mail? > > I had similar problems until I removed lpr from the base. > > To do this, I added this to /etc/make.conf: > > WITHOUT_LPR=true > > CUPS_OVERWRITE_BASE=yes > > NO_LPR=yes > > and then rebuilt and reinstalled world and cups. > > I have tried adding lpd_enable="NO" top rc.conf then realised > cups replaces lpd anyway so that was no help. > > Somewhere along the line I have added > > [system=10] > add path 'unlpt*' mode 0660 group cups > add path 'ulpt*' mode 0660 group cups > add path 'lpt*' mode 0660 group cups > > to /etc/devfs.rules and > > devfs_system_ruleset="system" > > to rc.conf > > I wanted to avoid having to buildword just now ... > > and just read this thead ; > > > CUPS installs its own version of lpr, lpq and lpd > > under /usr/local/bin. > > Therefore, be sure to delete lpr , lpq and lpd under > > /usr/bin and then symlink from /usr/local/bin to /usr/bin. > > although lpd looks to be under /usr/sbin on my system? You certainly shouldn't do this kind of random handiwork in your system. Nikola Lečić ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Selecting printer from apps core dumps. Howto debug?
(I proposed you a couple of things but generally it's a good idea to ask this on freebsd-gnome@ as well, since at least the Abiword problem is _maybe_ related to libgnomeprintui <-> Xfce.) On Sat, 30 Jun 2007 22:06:58 +0100 Graham Bentley <[EMAIL PROTECTED]> wrote: > > have you compiled print/xfce4-print with "Use cups as > > printing system"? This matters, among other things. You > > can check it with 'make showconfig' and change with > > 'make config'. > > 3bsd# make showconfig > ===> The following configuration options are available for > xfce4-print-4.4.1_1: LPR=off "Use lpr as printing system" > CUPS=on "Use cups as printing system" > LETTER=off "Use letter paper format instead of A4" > ===> Use 'make config' to modify these settings > 3bsd# Ok... > Its odd because the cups test page works, printing from > mousepad and firefox works, but abiword bombs completely. > In the short space of time I see it on the screen after > clicking print I can see there is no entry for the printer. AFAIK Abiword has known (and very old) problem with Xfce, mainly reflected in printing. As far as I understand it (I use neither Abiword nor CUPS) the cause could be the Abiword's (false) expectations of pure GNOME environment (including printing), which is only partially true in Xfce. You can try this, but I have no idea what can happen: # portupgrade -f -m 'WANT_GNOME=no' abiword Besides that, Claws Mail has by default similar expectations regarding printing (libgnomeprintui). Do you have printing problems in Claws Mail? Can you post here 'make showconfig" of mail/claws-mail? > > I had similar problems until I removed lpr from the base. > > To do this, I added this to /etc/make.conf: > > WITHOUT_LPR=true > > CUPS_OVERWRITE_BASE=yes > > NO_LPR=yes > > and then rebuilt and reinstalled world and cups. > > I have tried adding lpd_enable="NO" top rc.conf then realised > cups replaces lpd anyway so that was no help. > > Somewhere along the line I have added > > [system=10] > add path 'unlpt*' mode 0660 group cups > add path 'ulpt*' mode 0660 group cups > add path 'lpt*' mode 0660 group cups > > to /etc/devfs.rules and > > devfs_system_ruleset="system" > > to rc.conf > > I wanted to avoid having to buildword just now ... > > and just read this thead ; > > > CUPS installs its own version of lpr, lpq and lpd > > under /usr/local/bin. > > Therefore, be sure to delete lpr , lpq and lpd under > > /usr/bin and then symlink from /usr/local/bin to /usr/bin. > > although lpd looks to be under /usr/sbin on my system? You certainly shouldn't do this kind of random handiwork in your system. Nikola Lečić ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Selecting printer from apps core dumps. Howto debug?
> have you compiled print/xfce4-print with "Use cups as > printing system"? This matters, among other things. You > can check it with 'make showconfig' and change with > 'make config'. 3bsd# make showconfig ===> The following configuration options are available for xfce4-print-4.4.1_1: LPR=off "Use lpr as printing system" CUPS=on "Use cups as printing system" LETTER=off "Use letter paper format instead of A4" ===> Use 'make config' to modify these settings 3bsd# Its odd because the cups test page works, printing from mousepad and firefox works, but abiword bombs completely. In the short space of time I see it on the screen after clicking print I can see there is no entry for the printer. > I had similar problems until I removed lpr from the base. > To do this, I added this to /etc/make.conf: > WITHOUT_LPR=true > CUPS_OVERWRITE_BASE=yes > NO_LPR=yes > and then rebuilt and reinstalled world and cups. I have tried adding lpd_enable="NO" top rc.conf then realised cups replaces lpd anyway so that was no help. Somewhere along the line I have added [system=10] add path 'unlpt*' mode 0660 group cups add path 'ulpt*' mode 0660 group cups add path 'lpt*' mode 0660 group cups to /etc/devfs.rules and devfs_system_ruleset="system" to rc.conf I wanted to avoid having to buildword just now ... and just read this thead ; > CUPS installs its own version of lpr, lpq and lpd > under /usr/local/bin. > Therefore, be sure to delete lpr , lpq and lpd under > /usr/bin and then symlink from /usr/local/bin to /usr/bin. although lpd looks to be under /usr/sbin on my system? Any further help on figuring this out appreciated! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Selecting printer from apps core dumps. Howto debug?
On Thu, 2007-06-28 at 11:08 +0100, Graham Bentley wrote: > Hi FreeBSD'ers ! > > I have now a nice desktop setup with Xfce4 etc > thanks to all help from the list (what a great > place to be:) > > I have cups setup with a ppd to print to my usb > HP Busines Inkjet 1200. > > It works perfectly from doing the printer test > page from the cups webmin:631 page. > > In applications, if I select this printer, the > app core dumps. > > Apps effected are Abiword, the printer admin > xfprint4 in xfce4 and a few others. > > Who would I go about trying to diagnose this? > > Any help appreciated :) I had similar problems until I removed lpr from the base. To do this, I added this to /etc/make.conf: WITHOUT_LPR=true CUPS_OVERWRITE_BASE=yes NO_LPR=yes and then rebuilt and reinstalled world and cups. Now I can print from everything - including, impressively, Lotus Notes R5 running in wine. You probably only need one of WITHOUT_LPR/NO_LPR, but darned if I know which. The extra line in make.conf seemed simpler than trawling the makefiles. signature.asc Description: This is a digitally signed message part
Re: Selecting printer from apps core dumps. Howto debug?
On Thu, 28 Jun 2007 14:07:21 +0200 Nikola Lecic <[EMAIL PROTECTED]> wrote: > On Thu, 28 Jun 2007 11:08:26 +0100 > Graham Bentley <[EMAIL PROTECTED]> wrote: > > > Hi FreeBSD'ers ! > > > > I have now a nice desktop setup with Xfce4 etc > > thanks to all help from the list (what a great > > place to be:) > > > > I have cups setup with a ppd to print to my usb > > HP Busines Inkjet 1200. > > > > It works perfectly from doing the printer test > > page from the cups webmin:631 page. > > > > In applications, if I select this printer, the > > app core dumps. > > > > Apps effected are Abiword, the printer admin > > xfprint4 in xfce4 and a few others. > > > > Who would I go about trying to diagnose this? > > Hello David, have you compiled print/xfce4-print with "Use cups as > printing system"? This matters, among other things. You can check it > with 'make showconfig' and change with 'make config'. Graham, I trully appologise I typed the wrong name :( I somehow used the beginning of my previous post (sent to David Marec). Nikola ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Selecting printer from apps core dumps. Howto debug?
On Thu, 28 Jun 2007 11:08:26 +0100 Graham Bentley <[EMAIL PROTECTED]> wrote: > Hi FreeBSD'ers ! > > I have now a nice desktop setup with Xfce4 etc > thanks to all help from the list (what a great > place to be:) > > I have cups setup with a ppd to print to my usb > HP Busines Inkjet 1200. > > It works perfectly from doing the printer test > page from the cups webmin:631 page. > > In applications, if I select this printer, the > app core dumps. > > Apps effected are Abiword, the printer admin > xfprint4 in xfce4 and a few others. > > Who would I go about trying to diagnose this? Hello David, have you compiled print/xfce4-print with "Use cups as printing system"? This matters, among other things. You can check it with 'make showconfig' and change with 'make config'. Nikola Lečić ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Fw: Selecting printer from apps core dumps. Howto debug? [SOLVED]
Begin forwarded message: Date: Thu, 28 Jun 2007 11:08:26 +0100 From: Graham Bentley <[EMAIL PROTECTED]> To: freebsd-questions@freebsd.org Subject: Selecting printer from apps core dumps. Howto debug? Hi FreeBSD'ers ! I have now a nice desktop setup with Xfce4 etc thanks to all help from the list (what a great place to be:) I have cups setup with a ppd to print to my usb HP Busines Inkjet 1200. It works perfectly from doing the printer test page from the cups webmin:631 page. In applications, if I select this printer, the app core dumps. Apps effected are Abiword, the printer admin xfprint4 in xfce4 and a few others. Who would I go about trying to diagnose this? Any help appreciated :) [SOLVED] Set printer as 'default' using cups webmin. All working - thanks :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Selecting printer from apps core dumps. Howto debug?
Hi FreeBSD'ers ! I have now a nice desktop setup with Xfce4 etc thanks to all help from the list (what a great place to be:) I have cups setup with a ppd to print to my usb HP Busines Inkjet 1200. It works perfectly from doing the printer test page from the cups webmin:631 page. In applications, if I select this printer, the app core dumps. Apps effected are Abiword, the printer admin xfprint4 in xfce4 and a few others. Who would I go about trying to diagnose this? Any help appreciated :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Compile of Python 2.4.4 core dumps
Rob Gallagher wrote: On Wed, Feb 14, 2007 at 01:54:36PM +0100, Niclas Zeising wrote: Usually if a compile coredumps it's due to faulty memory or other hardware. Might be good to check that first. Especially since it worked flawlessly on another box. HTH //Niclas Thanks for the reply. I'm unsure if it's down to faulty memory because the machine is very new and I don't get core dumps when compiling or running any other software. Also, in my experience hardware faults have caused compiles to behave erraticlly, ie: bombing out at random stages in the build process - this core dump always occurs at exactly the same point (compilation of the curses module). I am experiencing the same problem (also running 6.2-RELEASE), so your hardware is not the cause. I'm afraid I don't have any helpful ideas, though. Bjørn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Compile of Python 2.4.4 core dumps
Hi Niclas, On Wed, Feb 14, 2007 at 01:54:36PM +0100, Niclas Zeising wrote: > > Usually if a compile coredumps it's due to faulty memory or other > hardware. Might be good to check that first. Especially since it > worked flawlessly on another box. > HTH > //Niclas > Thanks for the reply. I'm unsure if it's down to faulty memory because the machine is very new and I don't get core dumps when compiling or running any other software. Also, in my experience hardware faults have caused compiles to behave erraticlly, ie: bombing out at random stages in the build process - this core dump always occurs at exactly the same point (compilation of the curses module). ps: sorry about not wrapping my lines in the original post! ;-) rg -- "We have an announcement to make... uh... on July 4th of this year, America will blow up the moon." ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Compile of Python 2.4.4 core dumps
On 2/14/07, Rob Gallagher <[EMAIL PROTECTED]> wrote: Hi, Upgrading to latest version of python24 port (2.4.4), the compilation process core dumps shortly after it begins. Here is the output leading up to the core dump: cc -DNDEBUG -O2 -fno-strict-aliasing -pipe -D__wchar_t=wchar_t -DTHREAD_STACK_SIZE=0x2 -fPIC -fno-strict-aliasing -I. -I/usr/ports/lang/python24/work/Python-2.4.4/./Include -I/usr/local/include -I/usr/ports/lang/python24/work/Python-2.4.4/Include -I/usr/ports/lang/python24/work/Python-2.4.4 -c /usr/ports/lang/python24/work/Python-2.4.4/Modules/_cursesmodule.c -o build/temp.freebsd-6.2-RELEASE-i386-2.4/_cursesmodule.o cc -shared -pthread -O2 -fno-strict-aliasing -pipe -D__wchar_t=wchar_t -DTHREAD_STACK_SIZE=0x2 build/temp.freebsd-6.2-RELEASE-i386-2.4/_cursesmodule.o -L/usr/local/lib -lncurses -o build/lib.freebsd-6.2-RELEASE-i386-2.4/_curses.so Segmentation fault (core dumped) I'm running 6.2-RELEASE. I've upgraded another 6.2 box to python 2.4.4 without a problem, so I'm thinking the issue must lie with something on this system. rg Usually if a compile coredumps it's due to faulty memory or other hardware. Might be good to check that first. Especially since it worked flawlessly on another box. HTH //Niclas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Compile of Python 2.4.4 core dumps
Hi, Upgrading to latest version of python24 port (2.4.4), the compilation process core dumps shortly after it begins. Here is the output leading up to the core dump: cc -DNDEBUG -O2 -fno-strict-aliasing -pipe -D__wchar_t=wchar_t -DTHREAD_STACK_SIZE=0x2 -fPIC -fno-strict-aliasing -I. -I/usr/ports/lang/python24/work/Python-2.4.4/./Include -I/usr/local/include -I/usr/ports/lang/python24/work/Python-2.4.4/Include -I/usr/ports/lang/python24/work/Python-2.4.4 -c /usr/ports/lang/python24/work/Python-2.4.4/Modules/_cursesmodule.c -o build/temp.freebsd-6.2-RELEASE-i386-2.4/_cursesmodule.o cc -shared -pthread -O2 -fno-strict-aliasing -pipe -D__wchar_t=wchar_t -DTHREAD_STACK_SIZE=0x2 build/temp.freebsd-6.2-RELEASE-i386-2.4/_cursesmodule.o -L/usr/local/lib -lncurses -o build/lib.freebsd-6.2-RELEASE-i386-2.4/_curses.so Segmentation fault (core dumped) I'm running 6.2-RELEASE. I've upgraded another 6.2 box to python 2.4.4 without a problem, so I'm thinking the issue must lie with something on this system. rg -- "We have an announcement to make... uh... on July 4th of this year, America will blow up the moon." ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: core dumps
On 2006-11-10 12:40, Jim Pazarena <[EMAIL PROTECTED]> wrote: > is there any way to have NO core dumps? ..aside from never causing one :) > > I mean, can you compile something into the kernel to prevent core dumps? > I've never found it necessary to examine one in many years, and cannot > foresee ever having to do it. You don't have to compile anything into the kernel. There is a sysctl you can tweak, to enable and/or disable core dumps by processes: # sysctl kern.coredump=0 To make the setting permanent, set it in your `/etc/sysctl.conf' file too, without the 'sysctl' command: kern.coredump=0 - Giorgos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
core dumps
is there any way to have NO core dumps? ..aside from never causing one :) I mean, can you compile something into the kernel to prevent core dumps? I've never found it necessary to examine one in many years, and cannot foresee ever having to do it. Thx ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ZendOptimizer on FreeBSD 6.1 - Apache core dumps
Hi, We're about to purchase a software system that is encoded using Zend Guard and therefore we need to install the ZendOptimizer on our FreeBSD 6.1 STABLE server. The ZendOptimizer package has been installed from ports (allthough manually downloaded) and the needed text lines have been added to php.ini: [Zend] zend_optimizer.optimization_level=15 zend_extension_manager.optimizer="/usr/local/lib/php/20050922/Optimizer" zend_extension_manager.optimizer_ts="/usr/local/lib/php/20050922/Optimizer_TS" zend_extension="/usr/local/lib/php/20050922/ZendExtensionManager.so" [ THIS IS THE LINE THAT CAUSES THE PROBLEMS ] zend_extension_ts="/usr/local/lib/php/20050922/ZendExtensionManager_TS.so" However, when starting Apache (1.3.37 and php 5.1.6) it core dumps and won't start. I have posted a message in the Zend forums days ago without a reply and now it's getting urgent and I was hoping someone in here could provide us with some help. Here's the output from gdb: Reading symbols from /usr/local/lib/php/20050922/ZendExtensionManager.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/ZendExtensionManager.so Reading symbols from /usr/local/lib/php/20050922/ctype.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/ctype.so Reading symbols from /usr/local/lib/php/20050922/dom.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/dom.so Reading symbols from /usr/local/lib/php/20050922/ftp.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/ftp.so Reading symbols from /usr/lib/libssl.so.4...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libssl.so.4 Reading symbols from /lib/libcrypto.so.4...(no debugging symbols found)...done. Loaded symbols for /lib/libcrypto.so.4 Reading symbols from /usr/local/lib/php/20050922/iconv.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/iconv.so Reading symbols from /usr/local/lib/php/20050922/mysql.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/mysql.so Reading symbols from /usr/local/lib/mysql/libmysqlclient.so.14...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/mysql/libmysqlclient.so.14 Reading symbols from /usr/local/lib/php/20050922/pcre.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/pcre.so Reading symbols from /usr/local/lib/php/20050922/zlib.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/zlib.so Reading symbols from /usr/local/lib/php/20050922/pdo.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/pdo.so Reading symbols from /usr/local/lib/php/20050922/posix.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/posix.so Reading symbols from /usr/local/lib/php/20050922/session.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/session.so Reading symbols from /usr/local/lib/php/20050922/simplexml.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/simplexml.so Reading symbols from /usr/local/lib/php/20050922/sqlite.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/sqlite.so Reading symbols from /usr/local/lib/php/20050922/tokenizer.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/tokenizer.so Reading symbols from /usr/local/lib/php/20050922/xml.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/xml.so Reading symbols from /usr/local/lib/php/20050922/xmlreader.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/xmlreader.so Reading symbols from /usr/local/lib/php/20050922/xmlwriter.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/xmlwriter.so Reading symbols from /usr/local/lib/php/20050922/bz2.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/bz2.so Reading symbols from /usr/lib/libbz2.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libbz2.so.2 Reading symbols from /usr/local/lib/php/20050922/openssl.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/openssl.so Reading symbols from /usr/local/lib/php/20050922/mcrypt.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/mcrypt.so Reading symbols from /usr/local/lib/libmcrypt.so.8...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libmcrypt.so.8 Reading symbols from /usr/local/lib/libltdl.so.4...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libltdl.so.4 Reading symbols from /usr/local/lib/php/20050922/mbstr
Re: [SOLVED] Need help! Apache core dumps when running startssl
On 8/8/06, Andreas Widerøe Andersen <[EMAIL PROTECTED]> wrote: On 8/8/06, Girish Venkatachalam <[EMAIL PROTECTED]> wrote: > > > > --- Andreas Wider�e Andersen <[EMAIL PROTECTED]> > wrote: > > > On 8/8/06, [EMAIL PROTECTED] > > < [EMAIL PROTECTED]> wrote: > > > > > > Quoting Andreas Wider�e Andersen > > <[EMAIL PROTECTED]>: > > > > > > > On 8/8/06, [EMAIL PROTECTED] > > <[EMAIL PROTECTED]> wrote: > > > > > > > > > > Quoting Andreas Wider�e Andersen > > < [EMAIL PROTECTED]>: > > > > > > > > > > > (no debugging symbols found)...(no debugging > > symbols found)...(no > > > > > debugging > > > > > > symbols found)... > > > > > > Program received signal SIGPIPE, Broken > > pipe. > > > > > > 0x2810b1e8 in writev () from > > /usr/lib/libc.so.4 > > > > > > (gdb) > > > > > > > > > > And there's your problem. Some library did > > not link to libc > > > properly. Do > > > > > a > > > > > backtrace and a step, it will tell you which > > module is failing. > > > > > > > > > > I've had numerous problems like this in the > > past (mostly with mod_php > > > > > though), > > > > > recompiling the modules that gave errors > > sorted them out. > > > > > > > > > > I doubt this is a mod_ssl issue. > > > > > > > > > > > > Thanks. How do I find out which module is > > creating these problems? and > > > can I > > > > just recompile? I mean, what if it's a system > > module... > > > > > > As I said, use a backtrace > > > > > > gdb httpd httpd.core > > > run -X -DSSL > > > bt > > > step > > > > > > It should show you right up to the very line of > > code in the module that is > > > causing the crash... > > > > > > This is what I get now: > > > > (gdb) bt > > #0 0x283d1d61 in bn_mul_add_words () from > > /usr/local/lib/libcrypto.so.4 > > #1 0x8 in ?? () > > Error accessing memory address 0x55b7d3a2: Bad > > address. > > (gdb) step > > Single stepping until exit from function > > bn_mul_add_words, > > which has no line number information. > > > > Program terminated with signal SIGSEGV, Segmentation > > fault. > > The program no longer exists. > > (gdb) bt > > No stack. > > OpenSSL shared libraries are the culprit. Try > installing some other version of openssl and please > remember to build shared objects, IIRC it is > ./config --enable-shared > or something. > > That shud take care of ur problem. > > Best, > Girish I went into /usr/ports/security/openssl and did a make deinstall and then make reinstall and it worked! Now things are back normal again. Thanks a lot for all your help. Very much appreciated!!! Best regards from sunny Norway, Andreas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Need help! Apache core dumps when running startssl
On 8/8/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Quoting Andreas Widerøe Andersen <[EMAIL PROTECTED]>: > On 8/8/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > Quoting Andreas Widerøe Andersen <[EMAIL PROTECTED]>: > > > > > (no debugging symbols found)...(no debugging symbols found)...(no > > debugging > > > symbols found)... > > > Program received signal SIGPIPE, Broken pipe. > > > 0x2810b1e8 in writev () from /usr/lib/libc.so.4 > > > (gdb) > > > > And there's your problem. Some library did not link to libc properly. Do > > a > > backtrace and a step, it will tell you which module is failing. > > > > I've had numerous problems like this in the past (mostly with mod_php > > though), > > recompiling the modules that gave errors sorted them out. > > > > I doubt this is a mod_ssl issue. > > > Thanks. How do I find out which module is creating these problems? and can I > just recompile? I mean, what if it's a system module... As I said, use a backtrace gdb httpd httpd.core run -X -DSSL bt step It should show you right up to the very line of code in the module that is causing the crash... This is what I get now: (gdb) bt #0 0x283d1d61 in bn_mul_add_words () from /usr/local/lib/libcrypto.so.4 #1 0x8 in ?? () Error accessing memory address 0x55b7d3a2: Bad address. (gdb) step Single stepping until exit from function bn_mul_add_words, which has no line number information. Program terminated with signal SIGSEGV, Segmentation fault. The program no longer exists. (gdb) bt No stack. Best regards, Andreas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Need help! Apache core dumps when running startssl
On 8/8/06, Andreas Widerøe Andersen <[EMAIL PROTECTED]> wrote: On 8/8/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Quoting Andreas Widerøe Andersen <[EMAIL PROTECTED] >: > > > (no debugging symbols found)...(no debugging symbols found)...(no > debugging > > symbols found)... > > Program received signal SIGPIPE, Broken pipe. > > 0x2810b1e8 in writev () from /usr/lib/libc.so.4 > > (gdb) > > And there's your problem. Some library did not link to libc > properly. Do a > backtrace and a step, it will tell you which module is failing. > > I've had numerous problems like this in the past (mostly with mod_php > though), > recompiling the modules that gave errors sorted them out. > > I doubt this is a mod_ssl issue. Thanks. How do I find out which module is creating these problems? and can I just recompile? I mean, what if it's a system module... Sorry for all these questions, but this is a little above my head. :-) Best regards, Andreas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Need help! Apache core dumps when running startssl
Quoting Andreas Widerøe Andersen <[EMAIL PROTECTED]>: > (no debugging symbols found)...(no debugging symbols found)...(no debugging > symbols found)... > Program received signal SIGPIPE, Broken pipe. > 0x2810b1e8 in writev () from /usr/lib/libc.so.4 > (gdb) And there's your problem. Some library did not link to libc properly. Do a backtrace and a step, it will tell you which module is failing. I've had numerous problems like this in the past (mostly with mod_php though), recompiling the modules that gave errors sorted them out. I doubt this is a mod_ssl issue. -- C ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Need help! Apache core dumps when running startssl
On 8/8/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Quoting Andreas Widerøe Andersen <[EMAIL PROTECTED]>: > On 8/8/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > Quoting Girish Venkatachalam <[EMAIL PROTECTED]>: > > > > > > Hope to get some input. > > > > > Looks like ur random seeding is not happening > > > > > properly. check whether /dev/random and > > > > /dev/urandom > > > > > work properly. You can verify it with the command > > > > > > > > > > $openssl rand 512 > > > > > > > > > > > Why not just run httpd under gdb, and see WHY it is crashing? > > > > gdb httpd httpd.core > > > > run -X > > > > once cored, just back trace, step, and it should tell you exactly why it > > is > > crashing... > > > Thanks! > How do I start httpd with ssl support from this command? (I do apachectl > startssl when Apache crashes. apachectl start works fine though.) > > Apache runs fine when ssl is NOT started. run -X -DSSL Here's the output: # gdb httpd httpd.core GNU gdb 4.18 (FreeBSD) Copyright 1998 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-unknown-freebsd"...(no debugging symbols found)... Core was generated by `httpd'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libcrypt.so.2...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libmm.so.14...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libexpat.so.6...(no debugging symbols found)...done. Reading symbols from /usr/lib/libc.so.4...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_mmap_static.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_vhost_alias.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_env.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_define.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_log_config.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_mime_magic.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_mime.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_negotiation.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_status.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_info.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_include.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_autoindex.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_dir.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_cgi.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_asis.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_imap.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_actions.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_speling.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_userdir.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_alias.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_rewrite.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_access.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_auth.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_auth_anon.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_auth_db.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_digest.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/libproxy.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_cern_meta.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_expires.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_headers.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_usertrack.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/
Re: Need help! Apache core dumps when running startssl
Quoting Andreas Widerøe Andersen <[EMAIL PROTECTED]>: > On 8/8/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > Quoting Girish Venkatachalam <[EMAIL PROTECTED]>: > > > > > > Hope to get some input. > > > > > Looks like ur random seeding is not happening > > > > > properly. check whether /dev/random and > > > > /dev/urandom > > > > > work properly. You can verify it with the command > > > > > > > > > > $openssl rand 512 > > > > > > > > > > > Why not just run httpd under gdb, and see WHY it is crashing? > > > > gdb httpd httpd.core > > > > run -X > > > > once cored, just back trace, step, and it should tell you exactly why it > > is > > crashing... > > > Thanks! > How do I start httpd with ssl support from this command? (I do apachectl > startssl when Apache crashes. apachectl start works fine though.) > > Apache runs fine when ssl is NOT started. run -X -DSSL ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Need help! Apache core dumps when running startssl
On 8/8/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Quoting Girish Venkatachalam <[EMAIL PROTECTED]>: > > > > Hope to get some input. > > > Looks like ur random seeding is not happening > > > properly. check whether /dev/random and > > /dev/urandom > > > work properly. You can verify it with the command > > > > > > $openssl rand 512 > > > Why not just run httpd under gdb, and see WHY it is crashing? gdb httpd httpd.core run -X once cored, just back trace, step, and it should tell you exactly why it is crashing... Thanks! How do I start httpd with ssl support from this command? (I do apachectl startssl when Apache crashes. apachectl start works fine though.) Apache runs fine when ssl is NOT started. Thanks, Andreas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Need help! Apache core dumps when running startssl
[snip] Then that is working properly. I think you can try this then. Which might also work and I am out of ideas. :-( $ openssl genrsa 1024 # openssl genrsa 1024 Generating RSA private key, 1024 bit long modulus ...++ ...++ e is 65537 (0x10001) -BEGIN RSA PRIVATE KEY- [deleted] -END RSA PRIVATE KEY- Seems fine to me. It generates the key just like it should I think. Cheers, Andreas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Need help! Apache core dumps when running startssl
Quoting Girish Venkatachalam <[EMAIL PROTECTED]>: > > > > Hope to get some input. > > > Looks like ur random seeding is not happening > > > properly. check whether /dev/random and > > /dev/urandom > > > work properly. You can verify it with the command > > > > > > $openssl rand 512 > > > Why not just run httpd under gdb, and see WHY it is crashing? gdb httpd httpd.core run -X once cored, just back trace, step, and it should tell you exactly why it is crashing... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Need help! Apache core dumps when running startssl
--- Andreas Wider�e Andersen <[EMAIL PROTECTED]>
wrote:
> On 8/8/06, Girish Venkatachalam
> <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > --- Andreas Wider�e Andersen <[EMAIL PROTECTED]>
> > wrote:
> >
> > > Hi,
> > > I recently upgraded one of my production servers
> to
> > > FreeBSD 4.11 p19 and
> > > then upgraded all ports. I'm now running Apache
> > > 1.3.36 mod_ssl and Php 4.4.2
> > > .
> > >
> > > I had Squirrelmail running on https and now I
> can't
> > > start Apache with ssl.
> > > Every time it coredumps. I've tried snakeoil and
> my
> > > own cert. Same thing
> > > happens.
> > >
> > > This is the error message I can see from my
> > > httpd-error.log:
> > >
> > > [Mon Aug 7 20:20:03 2006] [notice] caught
> SIGTERM,
> > > shutting down
> > >
> > > ssl-engine log:
> > >
> > > [07/Aug/2006 20:29:01 16880] [info] Server:
> > > Apache/1.3.36, Interface:
> > > mod_ssl/2.8.27, Library: OpenSSL/0.9.8b
> > > [07/Aug/2006 20:29:01 16880] [info] Init: 1st
> > > startup round (still not
> > > detached)
> > > [07/Aug/2006 20:29:01 16880] [info] Init:
> > > Initializing OpenSSL library
> > > [07/Aug/2006 20:29:01 16880] [info] Init:
> Loading
> > > certificate & private key
> > > of SSL-aware server my.domain.com:443
> > > [07/Aug/2006 20:29:01 16880] [info] Init:
> Seeding
> > > PRNG with 136 bytes of
> > > entropy
> > > [07/Aug/2006 20:29:01 16880] [info] Init:
> > > Generating temporary RSA private
> > > keys (512/1024 bits)
> > >
> > > from messages:
> > >
> > > Aug 7 20:34:52 server /kernel: pid 17041
> (httpd),
> > > uid 0: exited on signal
> > > 11 (core dumped)
> > >
> > > That's it. I can't find any other logs and I
> can't
> > > tell what's wrong.
> > >
> > > What could it be and what can I do? I have
> checked
> > > the httpd.conf file and
> > > compared the previous version with the new dist.
> > > Same directives related to
> > > ssl virtualhost as far as I can see.
> > >
> > > Hope to get some input.
> > Looks like ur random seeding is not happening
> > properly. check whether /dev/random and
> /dev/urandom
> > work properly. You can verify it with the command
> >
> > $openssl rand 512
> >
> > HTH,
> > Girish
> >
>
> Thanks for your reply. This just gave me a lot of
> "garbage" on the screen.
> Ie, like this:
>
> ¿Ã3â¢Ãšï¼&â|¥¾W
>
jþâvzü¼ùµÃ¼}$(c)"swügþâ¬Ã±Â¿gé¶ïa°(c)éå4|Câ(c)\Ã
>
}â¢v=Ãñ5ÃÃ%âÃÃZ`Â",BÃÃTâ°â¹Ã¾BÅv´ýh£ÃlõKkòä2ZüìÃg{Ã¥Vµ±ü3`BæÃ(âºÂ¤>2çyõû12ÿNº9Ã
âùèkÃâ¢ÂºÃâ¦Â¼'âúÂÂ
>
> ...
Then that is working properly. I think you can try
this then. Which might also work and I am out of
ideas. :-(
$ openssl genrsa 1024
>
> Rgds,
> Andreas
>
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Need help! Apache core dumps when running startssl
On 8/8/06, Girish Venkatachalam <[EMAIL PROTECTED]> wrote: --- Andreas Wider�e Andersen <[EMAIL PROTECTED]> wrote: > Hi, > I recently upgraded one of my production servers to > FreeBSD 4.11 p19 and > then upgraded all ports. I'm now running Apache > 1.3.36 mod_ssl and Php 4.4.2 > . > > I had Squirrelmail running on https and now I can't > start Apache with ssl. > Every time it coredumps. I've tried snakeoil and my > own cert. Same thing > happens. > > This is the error message I can see from my > httpd-error.log: > > [Mon Aug 7 20:20:03 2006] [notice] caught SIGTERM, > shutting down > > ssl-engine log: > > [07/Aug/2006 20:29:01 16880] [info] Server: > Apache/1.3.36, Interface: > mod_ssl/2.8.27, Library: OpenSSL/0.9.8b > [07/Aug/2006 20:29:01 16880] [info] Init: 1st > startup round (still not > detached) > [07/Aug/2006 20:29:01 16880] [info] Init: > Initializing OpenSSL library > [07/Aug/2006 20:29:01 16880] [info] Init: Loading > certificate & private key > of SSL-aware server my.domain.com:443 > [07/Aug/2006 20:29:01 16880] [info] Init: Seeding > PRNG with 136 bytes of > entropy > [07/Aug/2006 20:29:01 16880] [info] Init: > Generating temporary RSA private > keys (512/1024 bits) > > from messages: > > Aug 7 20:34:52 server /kernel: pid 17041 (httpd), > uid 0: exited on signal > 11 (core dumped) > > That's it. I can't find any other logs and I can't > tell what's wrong. > > What could it be and what can I do? I have checked > the httpd.conf file and > compared the previous version with the new dist. > Same directives related to > ssl virtualhost as far as I can see. > > Hope to get some input. Looks like ur random seeding is not happening properly. check whether /dev/random and /dev/urandom work properly. You can verify it with the command $openssl rand 512 HTH, Girish Thanks for your reply. This just gave me a lot of "garbage" on the screen. Ie, like this: ¿Ð3•Éšï¼&–|¥¾W2çyõû12ÿNº9Å—ùèkÒ™ºß…¼'—ú ... Rgds, Andreas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Need help! Apache core dumps when running startssl
--- Andreas Wider�e Andersen <[EMAIL PROTECTED]> wrote: > Hi, > I recently upgraded one of my production servers to > FreeBSD 4.11 p19 and > then upgraded all ports. I'm now running Apache > 1.3.36 mod_ssl and Php 4.4.2 > . > > I had Squirrelmail running on https and now I can't > start Apache with ssl. > Every time it coredumps. I've tried snakeoil and my > own cert. Same thing > happens. > > This is the error message I can see from my > httpd-error.log: > > [Mon Aug 7 20:20:03 2006] [notice] caught SIGTERM, > shutting down > > ssl-engine log: > > [07/Aug/2006 20:29:01 16880] [info] Server: > Apache/1.3.36, Interface: > mod_ssl/2.8.27, Library: OpenSSL/0.9.8b > [07/Aug/2006 20:29:01 16880] [info] Init: 1st > startup round (still not > detached) > [07/Aug/2006 20:29:01 16880] [info] Init: > Initializing OpenSSL library > [07/Aug/2006 20:29:01 16880] [info] Init: Loading > certificate & private key > of SSL-aware server my.domain.com:443 > [07/Aug/2006 20:29:01 16880] [info] Init: Seeding > PRNG with 136 bytes of > entropy > [07/Aug/2006 20:29:01 16880] [info] Init: > Generating temporary RSA private > keys (512/1024 bits) > > from messages: > > Aug 7 20:34:52 server /kernel: pid 17041 (httpd), > uid 0: exited on signal > 11 (core dumped) > > That's it. I can't find any other logs and I can't > tell what's wrong. > > What could it be and what can I do? I have checked > the httpd.conf file and > compared the previous version with the new dist. > Same directives related to > ssl virtualhost as far as I can see. > > Hope to get some input. Looks like ur random seeding is not happening properly. check whether /dev/random and /dev/urandom work properly. You can verify it with the command $openssl rand 512 HTH, Girish > Thanks & Best regards, > Andreas W. Andersen > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Need help! Apache core dumps when running startssl
Hi, I recently upgraded one of my production servers to FreeBSD 4.11 p19 and then upgraded all ports. I'm now running Apache 1.3.36 mod_ssl and Php 4.4.2 . I had Squirrelmail running on https and now I can't start Apache with ssl. Every time it coredumps. I've tried snakeoil and my own cert. Same thing happens. This is the error message I can see from my httpd-error.log: [Mon Aug 7 20:20:03 2006] [notice] caught SIGTERM, shutting down ssl-engine log: [07/Aug/2006 20:29:01 16880] [info] Server: Apache/1.3.36, Interface: mod_ssl/2.8.27, Library: OpenSSL/0.9.8b [07/Aug/2006 20:29:01 16880] [info] Init: 1st startup round (still not detached) [07/Aug/2006 20:29:01 16880] [info] Init: Initializing OpenSSL library [07/Aug/2006 20:29:01 16880] [info] Init: Loading certificate & private key of SSL-aware server my.domain.com:443 [07/Aug/2006 20:29:01 16880] [info] Init: Seeding PRNG with 136 bytes of entropy [07/Aug/2006 20:29:01 16880] [info] Init: Generating temporary RSA private keys (512/1024 bits) from messages: Aug 7 20:34:52 server /kernel: pid 17041 (httpd), uid 0: exited on signal 11 (core dumped) That's it. I can't find any other logs and I can't tell what's wrong. What could it be and what can I do? I have checked the httpd.conf file and compared the previous version with the new dist. Same directives related to ssl virtualhost as far as I can see. Hope to get some input. Thanks & Best regards, Andreas W. Andersen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade core dumps
--- Neil Short <[EMAIL PROTECTED]> wrote: > Suddenly, portupgrade (and it's associated tools) > instantly core dumps. > followup: force reinstall/reregister of /usr/ports/lang/ruby18 did the trick. == Now I, Nebuchadnezzar, praise and extol and honor the King of heaven, for all his works are truth, and his ways are justice; and he is able to bring low those who walk in pride. Daniel 4:37 __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
portupgrade core dumps
Suddenly, portupgrade (and it's associated tools) instantly core dumps. any insight? Is my ports database boned? here is some sample output: bright# portupgrade portupgrade Segmentation fault (core dumped) bright# dmesg | tail pid 15403 (ruby18), uid 0: exited on signal 11 (core dumped) pid 15579 (ruby18), uid 0: exited on signal 11 (core dumped) pid 15770 (ruby18), uid 0: exited on signal 11 (core dumped) pid 15826 (ruby18), uid 0: exited on signal 11 (core dumped) pid 16045 (ruby18), uid 0: exited on signal 11 (core dumped) pid 16658 (gst-register-0.8), uid 0: exited on signal 11 (core dumped) pid 16711 (gtk-update-icon-cac), uid 0: exited on signal 11 (core dumped) pid 17069 (ruby18), uid 0: exited on signal 11 (core dumped) pid 17070 (ruby18), uid 0: exited on signal 11 (core dumped) pid 17081 (ruby18), uid 0: exited on signal 11 (core dumped) bright# cd /usr/ports/sysutils/portupgrade bright# make clean ===> Cleaning for ruby-1.8.4_8,1 ===> Cleaning for ruby18-bdb-0.5.9 ===> Cleaning for perl-5.8.8 ===> Cleaning for db41-4.1.25_3 ===> Cleaning for portupgrade-2.1.3.2,2 bright# make ===> Vulnerability check disabled, database not found ===> Extracting for portupgrade-2.1.3.2,2 => MD5 Checksum OK for pkgtools-2.1.3.2.tar.bz2. => SHA256 Checksum OK for pkgtools-2.1.3.2.tar.bz2. ===> portupgrade-2.1.3.2,2 depends on file: /usr/local/bin/ruby18 - found ===> Patching for portupgrade-2.1.3.2,2 ===> portupgrade-2.1.3.2,2 depends on file: /usr/local/bin/ruby18 - found ===> portupgrade-2.1.3.2,2 depends on file: /usr/local/bin/ruby18 - found ===> Configuring for portupgrade-2.1.3.2,2 ===> Building for portupgrade-2.1.3.2,2 ===> bin (all) Warning: Object directory not changed from original /usr/ports/sysutils/portupgrade/work/pkgtools-2.1.3.2/bin /usr/local/bin/ruby18 -wc pkg_fetch *** Signal 11 Stop in /usr/ports/sysutils/portupgrade/work/pkgtools-2.1.3.2/bin. *** Error code 1 Stop in /usr/ports/sysutils/portupgrade/work/pkgtools-2.1.3.2. *** Error code 1 Stop in /usr/ports/sysutils/portupgrade. bright# uname -a FreeBSD bright.sunset 7.0-CURRENT FreeBSD 7.0-CURRENT #2: Fri Jul 7 21:35:41 MST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BRIGHT i386 == Now I, Nebuchadnezzar, praise and extol and honor the King of heaven, for all his works are truth, and his ways are justice; and he is able to bring low those who walk in pride. Daniel 4:37 __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ipopd3 core dumps - can't log into pop3 server
Many mails from me here today. Sorry about that. Having more problems than skills I guess... I have upgraded to imap-uw-2004g_1,1 and now my users can't log into the server using pop3. Every time I try to log in from Ie. Eudora on my Windows box the ipop3 core dumps on the server. telnet my.domain.net 110 Trying 194.123.123.12... Connected to my.domain.net. Escape character is '^]'. +OK POP3 my.domain.net 2004.89 server ready -ERR Null command user testuser -ERR Unknown AUTHORIZATION state command I haven't seend this AUTHORIZATION message before. I want to allow both normal unencrypted password connections and let the user enable ssl if they know how to. Here are my inetd.conf mail details: imaps stream tcp nowait root/usr/local/libexec/imapd imapd pop3s stream tcp nowait root/usr/local/libexec/ipop3d ipop3d pop3stream tcp nowait root/usr/local/libexec/ipop3d ipop3d imap4 stream tcp nowait root/usr/local/libexec/imapdimapd This is what I have in my /etc/pam.conf file # Mail services imapauthrequiredpam_unix.so imapaccount requiredpam_unix.so imapsession requiredpam_unix.so pop3authrequiredpam_unix.so pop3account requiredpam_unix.so pop3session requiredpam_unix.so I have installed both cclient and imap-uw with the following directives: portinstall -m SSLTYPE=unix imap-uw (SSLTYPE=unix should be with ssl and plan text) I have also installed the following ports related to mail: openssl-0.9.8b_1SSL and crypto library cyrus-sasl-2.1.22 RFC SASL (Simple Authentication and Security Layer) cyrus-sasl-saslauthd-2.1.22 SASL authentication server for cyrus-sasl2 squirrelmail-1.4.6_1 A webmail system which accesses mail over IMAP telnet my.domain.net 110 Trying 194.123.123.12... Connected to my.domain.net. Escape character is '^]'. +OK POP3 my.domain.net 2004.89 server ready user testuser -ERR Unknown AUTHORIZATION state command Anyone out there who can give me some directions? Thanks! Andreas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: core dumps after kldloading snd_emu10kx.ko
ghostcorps wrote: Hi Guys I have to just say first, I'm pretty new to this, please be patient :) Firstly: $ uname -a FreeBSD ** 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 I recently added emu10kx ( http://www.freebsd.org/cgi/url.cgi?ports/audio/emu10kx/pkg-descr), but when I run kldload snd_emu10kx.ko the Kernel panics. As follows: Kernel trap 12 with interrupts disabled Fatal trap 12 : Page fault while in Kernel mode fault virtual address=0x74 fault code= Supervisor read, page not present instruction pointer = 0x20: 0xc0 657d4d stack pointer = 0x28: 0xef 71894c frame pointer = 0x28: 0xef 718950 Code segment=Base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def321, gran 1 Processor eflags= Resume, IOPL =0 Current process = 686 (kldload) Trap number =12 I can't find anyone with the same issue on google, so I guess the problem goes deeper that the sound card driver. Can anyone suggest where to start looking? Thanks in advance 1. Tell about this to the port maintainer of /usr/ports/audio/emu10kx ? 2. Try to use snd_emu10k1.ko from base system ? Sincerely, Tofik Suleymanov ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
core dumps after kldloading snd_emu10kx.ko
Hi Guys I have to just say first, I'm pretty new to this, please be patient :) Firstly: $ uname -a FreeBSD ** 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 I recently added emu10kx ( http://www.freebsd.org/cgi/url.cgi?ports/audio/emu10kx/pkg-descr), but when I run kldload snd_emu10kx.ko the Kernel panics. As follows: Kernel trap 12 with interrupts disabled Fatal trap 12 : Page fault while in Kernel mode fault virtual address=0x74 fault code= Supervisor read, page not present instruction pointer = 0x20: 0xc0 657d4d stack pointer = 0x28: 0xef 71894c frame pointer = 0x28: 0xef 718950 Code segment=Base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def321, gran 1 Processor eflags= Resume, IOPL =0 Current process = 686 (kldload) Trap number =12 I can't find anyone with the same issue on google, so I guess the problem goes deeper that the sound card driver. Can anyone suggest where to start looking? 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]"
jpilot core dumps on FreeBSD 6.1
Hi, I recently upgraded to FreeBSD 6.1. The only program that suddenly has problems with it is JPilot. It aborts when starting it with: ... jpilot in free(): error: modified (page-) pointer Abort trap (core dumped) ... I've synced my ports tree and reinstalled jpilot several times but nothing helps. Anyone else having this problem? Marco -- "My God! Are we sure he was a liberal?" "Pretty sure. They pulled him from a Volvo." ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Thunderbird segfaults and core dumps
For some reason, whenever I run thunderbird it segfaults and core dumps. I've uninstalled it and reinstalled it, but that didn't have any effect. any ideas? -Andrew ps. my system is running 6.0-CURRENT and thunderbird is version 1.5 thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portmanager core dumps
F. Even - fbsd-questions wrote: On Sunday 08 January 2006 18:30, Robert Marella wrote: Good Afternoon At times when in a hurry or not thinking as fast as my fingers, I try to run "portupgrade -s | grep OLD" from a regular user account instead of "sudo portupgrade -s | grep OLD". do you mean "portmanager -s | grep OLD" by any chance? I would expect portupgrade to insult my intelligence and question my heritage or is that question my intelligence and insult my heritage. Well, it doesn't do either. It core dumps. This will happen on more than one system running 6 Stable and the updated portmanager. [EMAIL PROTECTED] ~> pkg_info | grep portmanager portmanager-0.4.1_4 FreeBSD installed ports status and safe update utility Thanks Robert Portmanager will only run as root, I'll make a note/bug to check error handling when someone attempts to run it as a normal user. Mike, Please don't disable the ability to run this as a non-root user. I've managed to get it to run by chowning it's config, files under /var/db and the entire ports collection to an update user. Now I can run portmanager -s and it will give me an accurate run-down of what upgrades are needed. I can also then download updates as a restricted user. Changing to root will allow me to update as I need to, and as long as the src is cleaned up, no files owned by root are left behind in the ports tree. This actually works quite nicely. Thanks, Frank For the next few months I have no access to a FreeBSD system so won't be changing anything. Portmanager has no internal mechanisms for checking ownership, I think that so long as whoever has write access to everything in /usr/local/share/portmanager should be able to run it no problem. So if you want to change who can run it besides root just change the permisions of the files in that directory. I do have a change at home that moves the data bases to /var/db/portmanager so if that ever gets posted things will change slightly, it may never be posted though if no one takes over maintainership before I return. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portmanager core dumps
On Sunday 08 January 2006 18:30, Robert Marella wrote: Good Afternoon At times when in a hurry or not thinking as fast as my fingers, I try to run "portupgrade -s | grep OLD" from a regular user account instead of "sudo portupgrade -s | grep OLD". do you mean "portmanager -s | grep OLD" by any chance? I would expect portupgrade to insult my intelligence and question my heritage or is that question my intelligence and insult my heritage. Well, it doesn't do either. It core dumps. This will happen on more than one system running 6 Stable and the updated portmanager. [EMAIL PROTECTED] ~> pkg_info | grep portmanager portmanager-0.4.1_4 FreeBSD installed ports status and safe update utility Thanks Robert Portmanager will only run as root, I'll make a note/bug to check error handling when someone attempts to run it as a normal user. Mike, Please don't disable the ability to run this as a non-root user. I've managed to get it to run by chowning it's config, files under /var/db and the entire ports collection to an update user. Now I can run portmanager -s and it will give me an accurate run-down of what upgrades are needed. I can also then download updates as a restricted user. Changing to root will allow me to update as I need to, and as long as the src is cleaned up, no files owned by root are left behind in the ports tree. This actually works quite nicely. Thanks, Frank ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Mysql on freebsd strange core dumps
Hello, I'm running a mysql server mysql-server-4.1.16 on a FreeBSD 6.0-RELEASE-p1 and I'm constantly getting this: pid 82947 (mysqld), uid 88: exited on signal 11 (core dumped) (about 10-15 times a day). I ran the gdb debugger on the core dump and saw the following: Loaded symbols for /libexec/ld-elf.so.1 #0 0x2856365d in pthread_mutexattr_init () from /usr/lib/libpthread.so.2 [New Thread 0xd66cc00 (LWP 100090)] [New Thread 0xa9cfe00 (LWP 100207)] [New Thread 0xaa66c00 (LWP 100201)] [New Thread 0xab1b400 (LWP 100188)] [New Thread 0xa9cfa00 (LWP 100205)] [New Thread 0xd5f8200 (LWP 100203)] [New Thread 0xab1be00 (LWP 100204)] [New Thread 0xaa66800 (LWP 100193)] [New Thread 0xa926000 (LWP 100109)] [New Thread 0xa90aa00 (LWP 100120)] [New Thread 0xa90a600 (sleeping)] [New Thread 0xa90a400 (sleeping)] [New Thread 0xa90a200 (sleeping)] [New Thread 0xa90a000 (sleeping)] [New Thread 0x8454e00 (sleeping)] [New Thread 0x8454c00 (sleeping)] [New Thread 0x8454a00 (sleeping)] [New Thread 0x8454800 (LWP 100053)] Cannot get thread info: generic error Sorry for the long paste. Has anyone got any idea on how this might get fixed ? One thing I haven't tried again is to resync the sources and recompile the system base. (as libpthread seems to be part of the base system). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: azureus core dumps
On Jan 25, 2006, at 9:38 AM, Ion-Mihai Tetcu wrote: On Tue, 24 Jan 2006 16:54:27 +0200 [EMAIL PROTECTED] wrote: hi after upgrading linux_base and xorg-server azureus won't work anymore,i tried to reinstall all including java but no help.this is the log what azureus prints out after crashing,any help?thanks! As pointed out by a nice person on private, I didn't provide much info; here it is: # uname -a FreeBSD example.ro 6.0-STABLE FreeBSD 6.0-STABLE #10: Wed Jan 4 23:48:26 EET 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/IT6_U i386 # pkg_info -r azureus-2.3.0.6_1 Information for azureus-2.3.0.6_1: Depends on: Dependency: pkgconfig-0.20 Dependency: expat-1.95.8_3 Dependency: xorg-fonts-encodings-6.9.0 Dependency: xmlcatmgr-2.2 Dependency: freetype2-2.1.10_2 Dependency: jpeg-6b_3 Dependency: fontconfig-2.3.2,1 Dependency: xorg-libraries-6.9.0 Dependency: bitstream-vera-1.10_2 Dependency: sdocbook-xml-4.1.2.5_2 Dependency: docbook-xml-4.2_1 Dependency: openldap-client-2.2.30 Dependency: python-2.4.2 Dependency: libiconv-1.9.2_1 Dependency: png-1.2.8_2 Dependency: libxml2-2.6.23 Dependency: perl-5.8.7_2 Dependency: urwfonts-1.0 Dependency: hicolor-icon-theme-0.5 Dependency: samba-libsmbclient-3.0.21a Dependency: gettext-0.14.5 Dependency: popt-1.7 Dependency: glib-2.8.6 Dependency: shared-mime-info-0.16_2 Dependency: libgpg-error-1.1 Dependency: docbook-sk-4.1.2_3 Dependency: startup-notification-0.8_1 Dependency: p5-XML-Parser-2.34_1 Dependency: libgcrypt-1.2.2 Dependency: linc-1.0.3_4 Dependency: libXft-2.1.7 Dependency: libxslt-1.1.15 Dependency: libaudiofile-0.2.6 Dependency: libart_lgpl2-2.3.17 Dependency: glitz-0.4.4 Dependency: atk-1.10.3 Dependency: tiff-3.8.0 Dependency: cairo-1.0.2_1 Dependency: javavmwrapper-2.0_6 Dependency: xorg-fonts-truetype-6.9.0 Dependency: howl-1.0.0 Dependency: intltool-0.34.1 Dependency: pango-1.10.2 Dependency: jdk-1.4.2p7_2 Dependency: gtk-2.8.10 Dependency: gnome-icon-theme-2.12.1_2 Dependency: libglade2-2.5.1_3 Dependency: libIDL-0.8.6_1 Dependency: gnomehier-2.0_7 Dependency: ORBit2-2.12.4_1 Dependency: gconf2-2.12.1 Dependency: libbonobo-2.10.1_2 Dependency: libgnomecanvas-2.12.0 Dependency: gnomemimedata-2.4.2 Dependency: fam-2.6.9_6 Dependency: gnomevfs2-2.12.2 Dependency: esound-0.2.36 Dependency: docbook-xsl-1.69.1 Dependency: scrollkeeper-0.3.14_1,1 Dependency: libgnome-2.12.0.1 Dependency: libbonoboui-2.10.1_1 Dependency: gnomekeyring-0.4.6 Dependency: libgnomeui-2.12.0_1 Dependency: swt-3.1 -- IOnut Unregistered ;) FreeBSD "user" Course, submitting the core dumps to someone may help. There should be info in the handbook as to who to give it to. Also, I'll try cvsup'ing ports again and compiling stuff since I don't have it installed on my FreeBSD box. Another thing, are you using custom C[XX]FLAGS and what is your actual architecture (i386, amd64, etc)? -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: azureus core dumps
On Wed, 25 Jan 2006 09:29:53 -0800 Garrett Cooper <[EMAIL PROTECTED]> wrote: > > On Jan 25, 2006, at 9:07 AM, Ion-Mihai Tetcu wrote: > > > On Tue, 24 Jan 2006 16:54:27 +0200 > > [EMAIL PROTECTED] wrote: > > > >> hi > >> > >> after upgrading linux_base and xorg-server azureus won't work > >> anymore,i tried to reinstall all including java but no help.this is > >> the log what azureus prints out after crashing,any help?thanks! > > > > I'm not seeing this with ports from today on FreeBSD 6.0-STABLE #10: > > Wed Jan 4 23:48:26 EET 2006 > > Original requester: > Could you please provide information as to what architecture > you're using, as well as your version of FreeBSD, java, etc? You're right, sorry: # uname -a FreeBSD somehost.ro 6.0-STABLE FreeBSD 6.0-STABLE #10: Wed Jan 4 23:48:26 EET 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/IT6_U i386 # pkg_info -r azureus-2.3.0.6_1 Information for azureus-2.3.0.6_1: Depends on: Dependency: pkgconfig-0.20 Dependency: expat-1.95.8_3 Dependency: xorg-fonts-encodings-6.9.0 Dependency: xmlcatmgr-2.2 Dependency: freetype2-2.1.10_2 Dependency: jpeg-6b_3 Dependency: fontconfig-2.3.2,1 Dependency: xorg-libraries-6.9.0 Dependency: bitstream-vera-1.10_2 Dependency: sdocbook-xml-4.1.2.5_2 Dependency: docbook-xml-4.2_1 Dependency: openldap-client-2.2.30 Dependency: python-2.4.2 Dependency: libiconv-1.9.2_1 Dependency: png-1.2.8_2 Dependency: libxml2-2.6.23 Dependency: perl-5.8.7_2 Dependency: urwfonts-1.0 Dependency: hicolor-icon-theme-0.5 Dependency: samba-libsmbclient-3.0.21a Dependency: gettext-0.14.5 Dependency: popt-1.7 Dependency: glib-2.8.6 Dependency: shared-mime-info-0.16_2 Dependency: libgpg-error-1.1 Dependency: docbook-sk-4.1.2_3 Dependency: startup-notification-0.8_1 Dependency: p5-XML-Parser-2.34_1 Dependency: libgcrypt-1.2.2 Dependency: linc-1.0.3_4 Dependency: libXft-2.1.7 Dependency: libxslt-1.1.15 Dependency: libaudiofile-0.2.6 Dependency: libart_lgpl2-2.3.17 Dependency: glitz-0.4.4 Dependency: atk-1.10.3 Dependency: tiff-3.8.0 Dependency: cairo-1.0.2_1 Dependency: javavmwrapper-2.0_6 Dependency: xorg-fonts-truetype-6.9.0 Dependency: howl-1.0.0 Dependency: intltool-0.34.1 Dependency: pango-1.10.2 Dependency: jdk-1.4.2p7_2 Dependency: gtk-2.8.10 Dependency: gnome-icon-theme-2.12.1_2 Dependency: libglade2-2.5.1_3 Dependency: libIDL-0.8.6_1 Dependency: gnomehier-2.0_7 Dependency: ORBit2-2.12.4_1 Dependency: gconf2-2.12.1 Dependency: libbonobo-2.10.1_2 Dependency: libgnomecanvas-2.12.0 Dependency: gnomemimedata-2.4.2 Dependency: fam-2.6.9_6 Dependency: gnomevfs2-2.12.2 Dependency: esound-0.2.36 Dependency: docbook-xsl-1.69.1 Dependency: scrollkeeper-0.3.14_1,1 Dependency: libgnome-2.12.0.1 Dependency: libbonoboui-2.10.1_1 Dependency: gnomekeyring-0.4.6 Dependency: libgnomeui-2.12.0_1 Dependency: swt-3.1 -- IOnut Unregistered ;) FreeBSD "user" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: azureus core dumps
On Tue, 24 Jan 2006 16:54:27 +0200 [EMAIL PROTECTED] wrote: > hi > > after upgrading linux_base and xorg-server azureus won't work > anymore,i tried to reinstall all including java but no help.this is > the log what azureus prints out after crashing,any help?thanks! As pointed out by a nice person on private, I didn't provide much info; here it is: # uname -a FreeBSD example.ro 6.0-STABLE FreeBSD 6.0-STABLE #10: Wed Jan 4 23:48:26 EET 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/IT6_U i386 # pkg_info -r azureus-2.3.0.6_1 Information for azureus-2.3.0.6_1: Depends on: Dependency: pkgconfig-0.20 Dependency: expat-1.95.8_3 Dependency: xorg-fonts-encodings-6.9.0 Dependency: xmlcatmgr-2.2 Dependency: freetype2-2.1.10_2 Dependency: jpeg-6b_3 Dependency: fontconfig-2.3.2,1 Dependency: xorg-libraries-6.9.0 Dependency: bitstream-vera-1.10_2 Dependency: sdocbook-xml-4.1.2.5_2 Dependency: docbook-xml-4.2_1 Dependency: openldap-client-2.2.30 Dependency: python-2.4.2 Dependency: libiconv-1.9.2_1 Dependency: png-1.2.8_2 Dependency: libxml2-2.6.23 Dependency: perl-5.8.7_2 Dependency: urwfonts-1.0 Dependency: hicolor-icon-theme-0.5 Dependency: samba-libsmbclient-3.0.21a Dependency: gettext-0.14.5 Dependency: popt-1.7 Dependency: glib-2.8.6 Dependency: shared-mime-info-0.16_2 Dependency: libgpg-error-1.1 Dependency: docbook-sk-4.1.2_3 Dependency: startup-notification-0.8_1 Dependency: p5-XML-Parser-2.34_1 Dependency: libgcrypt-1.2.2 Dependency: linc-1.0.3_4 Dependency: libXft-2.1.7 Dependency: libxslt-1.1.15 Dependency: libaudiofile-0.2.6 Dependency: libart_lgpl2-2.3.17 Dependency: glitz-0.4.4 Dependency: atk-1.10.3 Dependency: tiff-3.8.0 Dependency: cairo-1.0.2_1 Dependency: javavmwrapper-2.0_6 Dependency: xorg-fonts-truetype-6.9.0 Dependency: howl-1.0.0 Dependency: intltool-0.34.1 Dependency: pango-1.10.2 Dependency: jdk-1.4.2p7_2 Dependency: gtk-2.8.10 Dependency: gnome-icon-theme-2.12.1_2 Dependency: libglade2-2.5.1_3 Dependency: libIDL-0.8.6_1 Dependency: gnomehier-2.0_7 Dependency: ORBit2-2.12.4_1 Dependency: gconf2-2.12.1 Dependency: libbonobo-2.10.1_2 Dependency: libgnomecanvas-2.12.0 Dependency: gnomemimedata-2.4.2 Dependency: fam-2.6.9_6 Dependency: gnomevfs2-2.12.2 Dependency: esound-0.2.36 Dependency: docbook-xsl-1.69.1 Dependency: scrollkeeper-0.3.14_1,1 Dependency: libgnome-2.12.0.1 Dependency: libbonoboui-2.10.1_1 Dependency: gnomekeyring-0.4.6 Dependency: libgnomeui-2.12.0_1 Dependency: swt-3.1 -- IOnut Unregistered ;) FreeBSD "user" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: azureus core dumps
On Jan 25, 2006, at 9:07 AM, Ion-Mihai Tetcu wrote: On Tue, 24 Jan 2006 16:54:27 +0200 [EMAIL PROTECTED] wrote: hi after upgrading linux_base and xorg-server azureus won't work anymore,i tried to reinstall all including java but no help.this is the log what azureus prints out after crashing,any help?thanks! I'm not seeing this with ports from today on FreeBSD 6.0-STABLE #10: Wed Jan 4 23:48:26 EET 2006 -- IOnut Unregistered ;) FreeBSD "user" Original requester: Could you please provide information as to what architecture you're using, as well as your version of FreeBSD, java, etc? -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: azureus core dumps
On Tue, 24 Jan 2006 16:54:27 +0200 [EMAIL PROTECTED] wrote: > hi > > after upgrading linux_base and xorg-server azureus won't work > anymore,i tried to reinstall all including java but no help.this is > the log what azureus prints out after crashing,any help?thanks! I'm not seeing this with ports from today on FreeBSD 6.0-STABLE #10: Wed Jan 4 23:48:26 EET 2006 -- IOnut Unregistered ;) FreeBSD "user" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
azureus core dumps
hi after upgrading linux_base and xorg-server azureus won't work anymore,i tried to reinstall all including java but no help.this is the log what azureus prints out after crashing,any help?thanks! An unexpected exception has been detected in native code outside the VM. Unexpected Signal : 11 occurred at PC=0x28745FB3 Function=inflate_fast+0x7B Library=/usr/local/jdk1.4.2/jre/lib/i386/libzip.so Current Java thread: at org.eclipse.swt.internal.gtk.OS._gtk_widget_size_request(Native Method) at org.eclipse.swt.internal.gtk.OS.gtk_widget_size_request(OS.java:7289) at org.eclipse.swt.widgets.Control.forceResize(Control.java:398) at org.eclipse.swt.widgets.Label.computeSize(Label.java:109) at org.eclipse.swt.layout.GridData.computeSize(GridData.java:478) at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:207) at org.eclipse.swt.layout.GridLayout.computeSize(GridLayout.java:155) at org.eclipse.swt.widgets.Composite.computeSize(Composite.java:192) at org.eclipse.swt.widgets.Control.pack(Control.java:852) at org.eclipse.swt.widgets.Control.pack(Control.java:827) at org.gudy.azureus2.ui.swt.mainwindow.SplashWindow.(Unknown Source) at org.gudy.azureus2.ui.swt.mainwindow.SplashWindow.(Unknown Source) at org.gudy.azureus2.ui.swt.mainwindow.SplashWindow$1.runSupport(Unknown Source) at org.gudy.azureus2.core3.util.AERunnable.run(Unknown Source) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) - locked <0x2ca43300> (a org.eclipse.swt.widgets.RunnableLock) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:2844) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2575) at org.gudy.azureus2.ui.swt.mainwindow.SWTThread.(Unknown Source) at org.gudy.azureus2.ui.swt.mainwindow.SWTThread.createInstance(Unknown Source) at org.gudy.azureus2.ui.swt.mainwindow.Initializer.(Unknown Source) at org.gudy.azureus2.ui.swt.Main.(Unknown Source) at org.gudy.azureus2.ui.swt.Main.main(Unknown Source) Dynamic libraries: 0x8048000 /usr/local/jdk1.4.2/bin/java 0x2808 /usr/lib/libpthread.so.2 0x280a9000 /lib/libc.so.6 0x281ad000 /usr/local/jdk1.4.2/jre/lib/i386/client/libjvm.so 0x28605000 /usr/lib/libstdc++.so.5 0x286db000 /lib/libm.so.4 0x286f4000 /usr/local/jdk1.4.2/jre/lib/i386/native_threads/libhpi.so 0x28702000 /usr/local/jdk1.4.2/jre/lib/i386/libverify.so 0x28718000 /usr/local/jdk1.4.2/jre/lib/i386/libjava.so 0x28736000 /usr/local/jdk1.4.2/jre/lib/i386/libzip.so 0x34ac6000 /usr/local/jdk1.4.2/jre/lib/i386/libnet.so 0x34c0 /usr/local/jdk1.4.2/jre/lib/i386/libnio.so 0x34c06000 /usr/local/lib/libswt-pi-gtk-3138.so 0x34c51000 /usr/X11R6/lib/libgtk-x11-2.0.so.0 0x34f4f000 /usr/local/lib/libgthread-2.0.so.0 0x34f53000 /usr/X11R6/lib/libXtst.so.6 0x34f58000 /usr/X11R6/lib/libgdk_pixbuf-2.0.so.0 0x34f6e000 /usr/X11R6/lib/libgdk-x11-2.0.so.0 0x34ffc000 /usr/X11R6/lib/libXrandr.so.2 0x3500 /usr/X11R6/lib/libXrender.so.1 0x35009000 /usr/X11R6/lib/libXi.so.6 0x2c4cd000 /usr/X11R6/lib/libXinerama.so.1 0x35011000 /usr/X11R6/lib/libXext.so.6 0x3502 /usr/X11R6/lib/libX11.so.6 0x3510 /usr/X11R6/lib/libpangocairo-1.0.so.0 0x35107000 /usr/X11R6/lib/libpangoft2-1.0.so.0 0x35134000 /usr/X11R6/lib/libfontconfig.so.1 0x35166000 /usr/local/lib/libfreetype.so.9 0x351ea000 /lib/libz.so.3 0x351ff000 /usr/X11R6/lib/libpango-1.0.so.0 0x3523a000 /usr/local/lib/libatk-1.0.so.0 0x35254000 /usr/local/lib/libgobject-2.0.so.0 0x3528f000 /usr/local/lib/libgmodule-2.0.so.0 0x35292000 /usr/local/lib/libglib-2.0.so.0 0x35319000 /usr/local/lib/libiconv.so.3 0x35408000 /usr/local/lib/libcairo.so.2 0x3546a000 /usr/local/lib/libintl.so.6 0x35474000 /usr/X11R6/lib/libXcursor.so.1 0x3547f000 /usr/X11R6/lib/libXfixes.so.3 0x35484000 /usr/local/lib/libexpat.so.5 0x354a2000 /usr/local/lib/libpng.so.5 0x354c5000 /usr/X11R6/lib/X11/locale/lib/common/xlcDef.so.2 0x354c8000 /usr/local/lib/libswt-gtk-3138.so 0x354fc000 /usr/X11R6/lib/gtk-2.0/2.4.0/engines/libpixmap.so 0x35505000 /usr/X11R6/lib/gtk-2.0/2.4.0/engines/libsvg.so 0x3550e000 /usr/X11R6/lib/librsvg-2.so.2 0x3553e000 /usr/local/lib/libart_lgpl_2.so.5 0x3555b000 /usr/local/lib/libcroco-0.6.so.3 0x35591000 /usr/local/lib/libxml2.so.5 0x356bd000 /usr/X11R6/lib/libgsf-1.so.113 0x356eb000 /usr/lib/libbz2.so.2 0x2804e000 /libexec/ld-elf.so.1 Heap at VM Abort: Heap def new generation total 576K, used 85K [0x2c4d, 0x2c57, 0x2c9b) eden space 512K, 11% used [0x2c4d, 0x2c4dea80, 0x2c55) from space 64K, 42% used [0x2c55, 0x2c556bc0, 0x2c56) to space 64K, 0% used [0x2c56, 0x2c56, 0x2c57) tenured generation total 1408K, used 1320K [0x2c9b, 0x2cb1, 0x304d) the space 1408K, 93% used [0x2c9b, 0x2cafa2e8, 0x2cafa400, 0x2cb1) compacting perm gen total 5632K, used 5491K [0x304d, 0x30a5, 0x344d) the space 5632K, 97% used [0x304d, 0x30a2cc90, 0x30a2ce00, 0x30a5) Local Time = Mon Jan 23 19:47:47 2006 Elapsed Time = 2 # #
Re: portmanager core dumps
On Sunday 08 January 2006 18:30, Robert Marella wrote: > Good Afternoon > > At times when in a hurry or not thinking as fast as my fingers, I try > to run "portupgrade -s | grep OLD" from a regular user account instead > of "sudo portupgrade -s | grep OLD". do you mean "portmanager -s | grep OLD" by any chance? > > I would expect portupgrade to insult my intelligence and question my > heritage or is that question my intelligence and insult my > heritage. Well, it doesn't do either. It core dumps. This will happen > on more than one system running 6 Stable and the updated portmanager. > > [EMAIL PROTECTED] ~> pkg_info | grep portmanager > portmanager-0.4.1_4 FreeBSD installed ports status and safe update > utility > > Thanks > > Robert Portmanager will only run as root, I'll make a note/bug to check error handling when someone attempts to run it as a normal user. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
portmanager core dumps
Good Afternoon At times when in a hurry or not thinking as fast as my fingers, I try to run "portupgrade -s | grep OLD" from a regular user account instead of "sudo portupgrade -s | grep OLD". I would expect portupgrade to insult my intelligence and question my heritage or is that question my intelligence and insult my heritage. Well, it doesn't do either. It core dumps. This will happen on more than one system running 6 Stable and the updated portmanager. [EMAIL PROTECTED] ~> pkg_info | grep portmanager portmanager-0.4.1_4 FreeBSD installed ports status and safe update utility Thanks Robert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portmanager -slid core dumps
On Friday 11 November 2005 14:53, Danny MacMillan wrote: > Michael C. Shultz wrote: > > On Friday 11 November 2005 13:35, Danny MacMillan wrote: > >>Michael C. Shultz wrote: > >>>On Friday 11 November 2005 12:55, Danny MacMillan wrote: > >>>>I am experiencing further difficulties with portmanager -slid. I was > >>>>successfully able to delete several leaf ports. However, when I try to > >>>>delete devel/p5-Locale-gettext or devel/gmake, portmanager core dumps > >>>>with the following message: > >>>> > >>>>... > >>>> Nuking gmake-3.80_2 > >>>> > >>>>MGdbGoTop error: invalid object type, has this object been initialised > >>>>with MGdbCreate or MGdbOpen yet? > >>>>MGdbSeek error: invalid object type > >>>>Assertion failed: (0), function MGdbSeek, file MGdbSeek.c, line 36. > >>>>zsh: abort (core dumped) sudo portmanager -slid > >>> > >>>What version of portmanager? > >> > >>rParseCommandLine 0.3.4_0 > > > > OK, that is the most current version. There isn't an obvious problem I > > can see in the code but there is something that can be done better so > > I'll make that change then we'll see what happens. Are you running > > FreeBSD 6.0 by any chance? > > Yes, I am. > > hobbit% uname -a > FreeBSD hobbit.emerald-associates.com 6.0-RELEASE FreeBSD 6.0-RELEASE > #0: Wed Nov 9 04:09:55 MST 2005 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/HOBBIT i386 This is why I didn't catch it earlier, 6.0 is more fussy about certain bad programming habits and I run 5.4. Probably would have never found this if you hadn't reported so thanks again. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portmanager -slid core dumps
Michael C. Shultz wrote: >>>>>>On Friday 11 November 2005 12:55, Danny MacMillan wrote: >>>>>>> >>>>>>>I am experiencing further difficulties with portmanager -slid. I was >>>>>>>successfully able to delete several leaf ports. However, when I try >>>>>>>to delete devel/p5-Locale-gettext or devel/gmake, portmanager core >>>>>>>dumps with the following message: >>>>>>> >>>>>>>... >>>>>>> Nuking gmake-3.80_2 >>>>>>> >>>>>>>MGdbGoTop error: invalid object type, has this object been initialised >>>>>>>with MGdbCreate or MGdbOpen yet? >>>>>>>MGdbSeek error: invalid object type >>>>>>>Assertion failed: (0), function MGdbSeek, file MGdbSeek.c, line 36. >>>>>>>zsh: abort (core dumped) sudo portmanager -slid > > OK, I found other stuff too, will post 0.3.4_1 tomorrow please wait till then > to use -slid ok? Will cooperate. Thank you for your kind attention. -- Danny MacMillan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portmanager -slid core dumps
On Friday 11 November 2005 15:02, Danny MacMillan wrote: > Michael C. Shultz wrote: > > On Friday 11 November 2005 14:21, you wrote: > >>On Friday 11 November 2005 13:35, Danny MacMillan wrote: > >>>Michael C. Shultz wrote: > >>>>On Friday 11 November 2005 12:55, Danny MacMillan wrote: > >>>>>I am experiencing further difficulties with portmanager -slid. I was > >>>>>successfully able to delete several leaf ports. However, when I try > >>>>> to delete devel/p5-Locale-gettext or devel/gmake, portmanager core > >>>>> dumps with the following message: > >>>>> > >>>>>... > >>>>> Nuking gmake-3.80_2 > >>>>> > >>>>>MGdbGoTop error: invalid object type, has this object been initialised > >>>>>with MGdbCreate or MGdbOpen yet? > >>>>>MGdbSeek error: invalid object type > >>>>>Assertion failed: (0), function MGdbSeek, file MGdbSeek.c, line 36. > >>>>>zsh: abort (core dumped) sudo portmanager -slid > >>>> > >>>>What version of portmanager? > >>> > >>>hobbit% sudo portmanager -v > >>>Password: > >>>rCreateCommandLineDb 0.3.4_0 info: executing rm -f > >>>/usr/local/share/portmanager/commandLine.db > >>> > >>>rParseCommandLine 0.3.4_0 > >> > >>OK, that is the most current version. There isn't an obvious problem I > >> can see in the code but there is something that can be done better so > >> I'll make that change then we'll see what happens. Are you running > >> FreeBSD 6.0 by any chance? > > > > Opps, found the bug, it would only happen if you used the small "n", big > > N or x or X should work ok untill I get a patch out. Thanks for > > reporting :) > > Sorry, Mike. For both devel/p5-Locale-gettext and devel/gmake, it > doesn't make any difference if I use 'n', 'N', 'x', or 'X'. I still get > exactly the same error. OK, I found other stuff too, will post 0.3.4_1 tomorrow please wait till then to use -slid ok? -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portmanager -slid core dumps
Michael C. Shultz wrote: > On Friday 11 November 2005 14:21, you wrote: >> >>On Friday 11 November 2005 13:35, Danny MacMillan wrote: >>> >>>Michael C. Shultz wrote: >>>> >>>>On Friday 11 November 2005 12:55, Danny MacMillan wrote: >>>>> >>>>>I am experiencing further difficulties with portmanager -slid. I was >>>>>successfully able to delete several leaf ports. However, when I try to >>>>>delete devel/p5-Locale-gettext or devel/gmake, portmanager core dumps >>>>>with the following message: >>>>> >>>>>... >>>>> Nuking gmake-3.80_2 >>>>> >>>>>MGdbGoTop error: invalid object type, has this object been initialised >>>>>with MGdbCreate or MGdbOpen yet? >>>>>MGdbSeek error: invalid object type >>>>>Assertion failed: (0), function MGdbSeek, file MGdbSeek.c, line 36. >>>>>zsh: abort (core dumped) sudo portmanager -slid >>>> >>>>What version of portmanager? >>> >>>hobbit% sudo portmanager -v >>>Password: >>>rCreateCommandLineDb 0.3.4_0 info: executing rm -f >>>/usr/local/share/portmanager/commandLine.db >>> >>>rParseCommandLine 0.3.4_0 >> >>OK, that is the most current version. There isn't an obvious problem I can >>see in the code but there is something that can be done better so I'll make >>that change then we'll see what happens. Are you running FreeBSD 6.0 >>by any chance? > > Opps, found the bug, it would only happen if you used the small "n", big N > or x or X should work ok untill I get a patch out. Thanks for reporting :) Sorry, Mike. For both devel/p5-Locale-gettext and devel/gmake, it doesn't make any difference if I use 'n', 'N', 'x', or 'X'. I still get exactly the same error. -- Danny MacMillan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portmanager -slid core dumps
Michael C. Shultz wrote: > On Friday 11 November 2005 13:35, Danny MacMillan wrote: >> >>Michael C. Shultz wrote: >>> >>>On Friday 11 November 2005 12:55, Danny MacMillan wrote: >>>> >>>>I am experiencing further difficulties with portmanager -slid. I was >>>>successfully able to delete several leaf ports. However, when I try to >>>>delete devel/p5-Locale-gettext or devel/gmake, portmanager core dumps >>>>with the following message: >>>> >>>>... >>>> Nuking gmake-3.80_2 >>>> >>>>MGdbGoTop error: invalid object type, has this object been initialised >>>>with MGdbCreate or MGdbOpen yet? >>>>MGdbSeek error: invalid object type >>>>Assertion failed: (0), function MGdbSeek, file MGdbSeek.c, line 36. >>>>zsh: abort (core dumped) sudo portmanager -slid >>> >>>What version of portmanager? >> >>rParseCommandLine 0.3.4_0 > > OK, that is the most current version. There isn't an obvious problem I can > see in the code but there is something that can be done better so I'll make > that change then we'll see what happens. Are you running FreeBSD 6.0 > by any chance? Yes, I am. hobbit% uname -a FreeBSD hobbit.emerald-associates.com 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Wed Nov 9 04:09:55 MST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/HOBBIT i386 -- Danny MacMillan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portmanager -slid core dumps
On Friday 11 November 2005 14:21, you wrote: > On Friday 11 November 2005 13:35, Danny MacMillan wrote: > > Michael C. Shultz wrote: > > > On Friday 11 November 2005 12:55, Danny MacMillan wrote: > > >>I am experiencing further difficulties with portmanager -slid. I was > > >>successfully able to delete several leaf ports. However, when I try to > > >>delete devel/p5-Locale-gettext or devel/gmake, portmanager core dumps > > >>with the following message: > > >> > > >>... > > >> Nuking gmake-3.80_2 > > >> > > >>MGdbGoTop error: invalid object type, has this object been initialised > > >>with MGdbCreate or MGdbOpen yet? > > >>MGdbSeek error: invalid object type > > >>Assertion failed: (0), function MGdbSeek, file MGdbSeek.c, line 36. > > >>zsh: abort (core dumped) sudo portmanager -slid > > > > > > What version of portmanager? > > > > hobbit% sudo portmanager -v > > Password: > > rCreateCommandLineDb 0.3.4_0 info: executing rm -f > > /usr/local/share/portmanager/commandLine.db > > > > rParseCommandLine 0.3.4_0 > > OK, that is the most current version. There isn't an obvious problem I can > see in the code but there is something that can be done better so I'll make > that change then we'll see what happens. Are you running FreeBSD 6.0 > by any chance? > > -Mike Opps, found the bug, it would only happen if you used the small "n", big N or x or X should work ok untill I get a patch out. Thanks for reporting :) -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portmanager -slid core dumps
On Friday 11 November 2005 13:35, Danny MacMillan wrote: > Michael C. Shultz wrote: > > On Friday 11 November 2005 12:55, Danny MacMillan wrote: > >>I am experiencing further difficulties with portmanager -slid. I was > >>successfully able to delete several leaf ports. However, when I try to > >>delete devel/p5-Locale-gettext or devel/gmake, portmanager core dumps > >>with the following message: > >> > >>... > >> Nuking gmake-3.80_2 > >> > >>MGdbGoTop error: invalid object type, has this object been initialised > >>with MGdbCreate or MGdbOpen yet? > >>MGdbSeek error: invalid object type > >>Assertion failed: (0), function MGdbSeek, file MGdbSeek.c, line 36. > >>zsh: abort (core dumped) sudo portmanager -slid > > > > What version of portmanager? > > hobbit% sudo portmanager -v > Password: > rCreateCommandLineDb 0.3.4_0 info: executing rm -f > /usr/local/share/portmanager/commandLine.db > > rParseCommandLine 0.3.4_0 OK, that is the most current version. There isn't an obvious problem I can see in the code but there is something that can be done better so I'll make that change then we'll see what happens. Are you running FreeBSD 6.0 by any chance? -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portmanager -slid core dumps
Michael C. Shultz wrote: > On Friday 11 November 2005 12:55, Danny MacMillan wrote: >> >>I am experiencing further difficulties with portmanager -slid. I was >>successfully able to delete several leaf ports. However, when I try to >>delete devel/p5-Locale-gettext or devel/gmake, portmanager core dumps >>with the following message: >> >>... >> Nuking gmake-3.80_2 >> >>MGdbGoTop error: invalid object type, has this object been initialised >>with MGdbCreate or MGdbOpen yet? >>MGdbSeek error: invalid object type >>Assertion failed: (0), function MGdbSeek, file MGdbSeek.c, line 36. >>zsh: abort (core dumped) sudo portmanager -slid > > What version of portmanager? hobbit% sudo portmanager -v Password: rCreateCommandLineDb 0.3.4_0 info: executing rm -f /usr/local/share/portmanager/commandLine.db rParseCommandLine 0.3.4_0 -- Danny MacMillan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portmanager -slid core dumps
On Friday 11 November 2005 12:55, Danny MacMillan wrote: > Hi, > > I am experiencing further difficulties with portmanager -slid. I was > successfully able to delete several leaf ports. However, when I try to > delete devel/p5-Locale-gettext or devel/gmake, portmanager core dumps > with the following message: > > ... > Nuking gmake-3.80_2 > > MGdbGoTop error: invalid object type, has this object been initialised > with MGdbCreate or MGdbOpen yet? > MGdbSeek error: invalid object type > Assertion failed: (0), function MGdbSeek, file MGdbSeek.c, line 36. > zsh: abort (core dumped) sudo portmanager -slid > > Are there any practices I should be following in order to ensure > consistency of my ports tree? In particular, are there any deleterious > consequences of using "make deinstall" to remove a port that has been > updated since it was installed? What version of portmanager? portmanager -v -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
portmanager -slid core dumps
Hi, I am experiencing further difficulties with portmanager -slid. I was successfully able to delete several leaf ports. However, when I try to delete devel/p5-Locale-gettext or devel/gmake, portmanager core dumps with the following message: ... Nuking gmake-3.80_2 MGdbGoTop error: invalid object type, has this object been initialised with MGdbCreate or MGdbOpen yet? MGdbSeek error: invalid object type Assertion failed: (0), function MGdbSeek, file MGdbSeek.c, line 36. zsh: abort (core dumped) sudo portmanager -slid Are there any practices I should be following in order to ensure consistency of my ports tree? In particular, are there any deleterious consequences of using "make deinstall" to remove a port that has been updated since it was installed? -- Danny MacMillan ___ 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]"
