Segmentation fault!
Hello! I run FreeBSD 5.2.1 FreeBSD belea.mine.nu 5.2.1-RELEASE FreeBSD 5.2.1-RELEASE #0: Mon Feb 23 20:45:55 GMT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 I installed it couple weeks ago! Yesterday i tried /stand/sysintall and i get this ugly error: Segmentation fault (core dumped) /stand/sysinstall worked fine by 2 days ago ... What should i do? Thank you! _ Tired of spam? Get [2]advanced junk mail protection with MSN 8. References 1. mailto:[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC 2. http://g.msn.com/8HMAEN/2734??PS= ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
segmentation fault
i am trying to run a portupgrade and have a problem. portupgrade says i have a stale dependency and need to fix it with pkgdb, when i run that, i get this guinness# pkgdb -F ---> Checking the package registry database Stale dependency: php4-4.3.5_7 -> apache-1.3.29_3 (www/apache13): [Failed `Inappropriate file type or format'] [Updating the portsdb in /usr/ports ... - 11973 port entries found .1000.2000.3000.4000.5000/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:587: [BUG] Segmentation fault ruby 1.8.2 (2004-07-29) [i386-freebsd4] Abort (core dumped) i rebuilt the ports index by going to /usr/ports and doing make index, but i still get this same deal. whats up? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
getmail Segmentation fault
Hi, After upgrading to the newest Python 2.4.3, I always get a Segmentation fault after running getmail using ssl connection. This problem doesn't show up for ordinary pop3 connections without ssl. Is it related to the the ssl library of freebsd? By the way, I'm using freebsd6.0 and getmail 4.5.4. Regards, -- Zeng Nan Simple is Beautiful. MY BLOG: http://zengnan.blogspot.com Public Key: http://pgp.mit.edu/ | www.keyserver.net pgp2pB8hE8tAK.pgp Description: PGP signature
tar segmentation fault
Hello, I want to backup certain parts of my system regularly, so I made a directory which reflects the filesystem: backup/ etc/ -> link to /etc usr/ home/ me/ somefile -> link to some specific file in my home directory public_html/ various_links_to/ -> directories_which/ -> really_exist_in_my/ -> public_html/ -> Basically it's a collection of symlinks to stuff I want backed up. Then I run tar -cLvy -f /usr/home/me/backup/backup.tar.bz2 /usr/home/me/backup/source/ When source/usr/home/me/public_html is empty then it runs fine. But when I put any links in, tar dies with a segmentation fault. Has anyone got any ideas why? Thanks, Ben ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Segmentation fault (11)
This is a questions to the group since I'm not sure if it's related to my FreeBSD 5.4 OS or something else. I'm on a Dell Pentium 2.55Ghz with 1 GB Ram. Background: In trying to install oscommerce I have uninstalled my php5 and went to php4. Because of error I've reinstalled Apache 1.3 and Perl5. My database is MySQL 5.02. The problem: when I attempt to open an index.php file in the oscommerce program I get, in my httpd-error.log [notice] child pid xxx exit signal Segmentation fault(11) All other php related sites are functioning well with no problems. Do you believe this is being caused by the code in the oscommerce program or something FreeBSD is doing? Thanks for input Dean Lasiter Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Segmentation fault (11)
This is a questions to the group since I'm not sure if it's related to my FreeBSD 5.4 OS or something else. I'm on a Dell Pentium 2.55Ghz with 1 GB Ram. Background: In trying to install oscommerce I have uninstalled my php5 and went to php4. Because of error I've reinstalled Apache 1.3 and Perl5. My database is MySQL 5.02. The problem: when I attempt to open an index.php file in the oscommerce program I get, in my httpd-error.log [notice] child pid xxx exit signal Segmentation fault(11) All other php related sites are functioning well with no problems. Do you believe this is being caused by the code in the oscommerce program or something FreeBSD is doing? Thanks for input Dean Lasiter __ Yahoo! Mail for Mobile Take Yahoo! Mail with you! Check email on your mobile phone. http://mobile.yahoo.com/learn/mail ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
portsnap segmentation fault
When I run portsnap update, I get the following error after it extracts the files: Building new INDEX files... Segmentation fault (core dumped) This is occuring on three different machines, so I'm guessing it's a problem with portsnap, not my one machine. But they all have similar configurations, so it could be my setup, I don't know. Any ideas what's going on? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Apache segmentation fault
Upgraded php52 to php53 by pkg_delete of php5 and porinstall php52. Then I had to manually resort back to php52 by pkg_delete and then portinstall and now getting a seg fault when restarting apache22 on this FreeBSD 8.1 server. I narrowed it down to not the php module, but the two ldap modules I have in apache... mail# cat httpd.conf|grep ldap #LoadModule authnz_ldap_module libexec/apache22/mod_authnz_ldap.so #LoadModule ldap_module libexec/apache22/mod_ldap.so With these two lines commented out, apache restarts without the seg fault. Tried to force pkg_delete on apache and then portinstall to rebuild these modules, but same issue afterward. The php module loads without error, but getting download prompts when trying to access php pages. Not getting any help from messages or httpd-error logs and all was working before I messed it up. My question is what I should try next to try and fix this issue. Should I force pkg_delete and rebuild all php packages or ldap packages? Or some other approach? Thanks for any help, Robert -- Robert ___ 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"
w3m - Segmentation fault
Hello, I try today install port w3m (www/w3m) and got segmentation fault. Is somone else have such trouble? FreeBSD 7.2-RELEASE, AMD64. # make install clean ... cc -I. -I. -O2 -fno-strict-aliasing -pipe -I/usr/include/openssl -I/usr/local/include -I/usr/local/include -DHAVE_CONFIG_H -DAUXBIN_DIR=\"/usr/local/libexec/w3m\" -DCGIBIN_DIR=\"/usr/local/libexec/w3m/cgi-bin\" -DHELP_DIR=\"/usr/local/share/w3m\" -DETC_DIR=\"/usr/local/etc\" -DCONF_DIR=\"/usr/local/etc/w3m\" -DRC_DIR=\"~/.w3m\" -DLOCALEDIR=\"/usr/local/share/locale\" -c myctype.c cc -I. -I. -O2 -fno-strict-aliasing -pipe -I/usr/include/openssl -I/usr/local/include -I/usr/local/include -DHAVE_CONFIG_H -DAUXBIN_DIR=\"/usr/local/libexec/w3m\" -DCGIBIN_DIR=\"/usr/local/libexec/w3m/cgi-bin\" -DHELP_DIR=\"/usr/local/share/w3m\" -DETC_DIR=\"/usr/local/etc\" -DCONF_DIR=\"/usr/local/etc/w3m\" -DRC_DIR=\"~/.w3m\" -DLOCALEDIR=\"/usr/local/share/locale\" -c hash.c ar rv libindep.a Str.o indep.o regex.o textlist.o parsetag.o myctype.o hash.o ar: creating libindep.a a - Str.o a - indep.o a - regex.o a - textlist.o a - parsetag.o a - myctype.o a - hash.o ranlib libindep.a cc -I. -I. -O2 -fno-strict-aliasing -pipe -I/usr/include/openssl -I/usr/local/include -I/usr/local/include -DHAVE_CONFIG_H -DAUXBIN_DIR=\"/usr/local/libexec/w3m\" -DCGIBIN_DIR=\"/usr/local/libexec/w3m/cgi-bin\" -DHELP_DIR=\"/usr/local/share/w3m\" -DETC_DIR=\"/usr/local/etc\" -DCONF_DIR=\"/usr/local/etc/w3m\" -DRC_DIR=\"~/.w3m\" -DLOCALEDIR=\"/usr/local/share/locale\" -o mktable mktable.o dummy.o -L/usr/local/lib -lm -L. -lindep -L/usr/local/lib -lgc sort funcname.tab | nawk -f ./functable.awk > functable.tab ./mktable 100 functable.tab > functable.c Segmentation fault (core dumped) *** Error code 139 Stop in /usr/ports/www/w3m/work/w3m-0.5.2. *** Error code 1 Stop in /usr/ports/www/w3m. ___ 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"
Ettercap segmentation fault....
Hello, I have compiles ettercap from ports without incident. However, when I attempt to run ettercap in any way, after a short while the program crashes and I am presented with an error message which is as follows: Ooops ! This shouldn't happen... Segmentation Fault... Please recompile in debug mode, reproduce the bug and send a bugreport I have deinstalled and recompiled to program twice, yielding no results. Some additional information which may be useful- #pkg_info | grep ettercap ettercap-gtk2-0.7.3_10,1 A network sniffer/interceptor/injector/logger for switched #uname -a FreeBSD 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC 2009 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 If anyone wishes me to recompile in debug mode, you will have to tell me how; I am not familiar with the process. Axel___ 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"
segmentation fault 11
I saw a reference that linux.ko and kqemu.ko can start a segmentation fault 11. My memory is set to 2G in the loader file and physical is 1.77G. Would this cause the problem? _ See how Windows Mobile brings your life together—at home, work, or on the go. http://clk.atdmt.com/MRT/go/msnnkwxp1020093182mrt/direct/01/___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
PHP5 segmentation fault
Hello everyone, this is my first post to the list as I am a new FreeBSD user as of last week. I've installed 7.0RC1 amd64 architecture on my poweredge 2950. I'm having issues with apache22 and php5. Here is the process I went through to install both. 1. Installed www/apache22 using 'make install clean' with default config options. 2. Installed lang/php5 using 'make install clean' with default config options plus apache support. Apache seems to be working fine w/o php5 but after I install php5, apache will core dump on restart. PHP5 also seg faults when executing /usr/local/bin/php # /usr/local/bin/php Segmentation fault: 11 (core dumped) Any suggestions would be very appreciative. Thanks! -- Jeffrey Lehman http://digitalguy.net GPG Key fingerprint = 3087 CED0 57F7 3BD3 14E7 969B EE14 BADA D619 8CF5 pgpK13fe5D6qh.pgp Description: PGP signature
tor, segmentation fault.
Hello. Does anybody there have experience how to run an ports/security/tor ? I have use FreeBSD 4.11-RELEASE-p13 and "tor" here always exit with signal 11 and Segmentation fault message. -- dima <7509107*mail,ru> <2:550/112> ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
spumux segmentation fault
Hi everybody! Here is one more problem to solve. Even if I don't put any options for spumux on command line, a segmentation fault is thrown. $ spumux DVDAuthor::spumux, version 0.6.14. Build options: gnugetopt magick iconv freetype fribidi Send bugs to <[EMAIL PROTECTED]> Segmentation fault (core dumped) $ uname -a FreeBSD xxx.yyy.com 6.2-STABLE FreeBSD 6.2-STABLE #0: Wed Jul 11 06:07:39 PDT 2007 root@:/usr/obj/usr/src/sys/AMD64 amd64 What can I do to fix the problem? Thank you in advance! Andriy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Segmentation fault: _pthread_mutex_init_calloc_cb()
Hi all When my C program executing exit(EX_OK); I get following error message in ddd: Program received signal SIGSEGV, Segmentation fault. 0x28102600 in _pthread_mutex_init_calloc_cb () from /lib/libc.so.7 I'm running FreeBSD 7.0 on i386. I noted I got this issue after I introduced a code section with strsep. I'm not sure whether there is anything to do with strsep, ddd shows strsep works well. Any idea what is wrong? Many thanks in advance. kind regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Segmentation Fault Question
Hey everyone, I am running version 4.3 and I am running into the following problem. When running one of the commands in vpopmail, I am getting a core dump (segmentation fault). There is no obvious vpopmail answer, so I'm thinking it might be system related. I ran ktrace/kdump on the process, and here are the last few lines of the output: 77402 vpasswd RET write 8192/0x2000 77402 vpasswd PSIG SIGSEGV SIG_DFL 77402 vpasswd NAMI "vpasswd.core" Can anyone tell me why I am getting segmentation faults? Let me know if you need any more info. The configuration of the system hasn't been changed and everything was working fine until recently, when the command started generating these errors. TIA Brendan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ruby1.8 segmentation fault
Hi BSDers, I read the ports/UPDATING about ruby stuff and do accordingly, after reinstall portupgrade, I did "portupgrade -fr /usr/ports/land/ruby16" and here it goes: [Updating the pkgdb in /var/db/pkg ... - 435 packages found (-22 +61) (...)/usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:467: [BUG] Segmentation fault ruby 1.8.1 (2003-12-25) [i386-freebsd4] Abort (core dumped) dont' have the balls the mess with this stuff, so...any idea? Eureka! Best regards ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
segmentation fault - jdk4
Hi, I'm running 5.2.1 Release version of FreeBSD, gcc 3.3.3 and I'm getting the same error when trying to compile JDK 1.4 from ports: *any_file_that_changes.c or .h*: *number_that_changes*: compiler error: segmentation fault I've searched for information and people say that could be problems with gcc or hardware (memory for eg.). I tried to install new version of gcc (3.4.0) and still continues using the older (3.3.3), tried the 3.2 and the error continues. About the hardware...everything seems to be fine. Do you have any suggestions? people through net didn't find any reasonable cause. I appreciate your attention, Best regards, Ricardo ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
time() segmentation fault
Hi all,
this program ends with a segmentation fault in a FreeBSD 5.1.2-RELEASE:
main() { time(); }
I don't have made important changes to the release except cosmetic ones. I'm
running the Linux compatibility module and have compiled with gcc 3.3.3. Any
ideas are welcome.
Abel
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
apache segmentation fault
OS: FreeBSD 4.8 Stable Server: Apache/1.3.28 (Unix) mod_perl/1.27 PHP/4.3.3RC2 PHP/3.0.18 mod_ssl/2.8.15 OpenSSL/0.9.7a mod_fastcgi/2.4.0 Hi, well didnt get a response to the first post. I think I am asking the proper questions. please let me know if I am not and let me know what I need to include to get this situation expressed properly. I keep coming upon a segmentation fault with apache. I dont know what is causing it. I think I have a core file lying around on the machine when this happens. what is a good course of action to figure out what is going on here? how can I analyze the core file to figure out what is going on. from the apache logs [Mon Aug 25 10:02:04 2003] [notice] child pid 2266 exit signal Segmentation faul t (11) a core file search - nothing found shell# find / -name "httpd\.core" so how can I generate a core file when apache has a segmentatino fault? - Noah ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: segmentation fault
On Saturday 20 November 2004 11:39 am, Steel City Phantom wrote: > i am trying to run a portupgrade and have a problem. portupgrade says i > have a stale dependency and need to fix it with pkgdb, when i run that, > i get this > > guinness# pkgdb -F > ---> Checking the package registry database > Stale dependency: php4-4.3.5_7 -> apache-1.3.29_3 (www/apache13): > [Failed `Inappropriate file type or format'] [Updating the portsdb > in /usr/ports ... - 11973 port entries found > .1000.2000.3000.4000.5000/u >sr/local/lib/ruby/site_ruby/1.8/portsdb.rb:587: [BUG] Segmentation fault > ruby 1.8.2 (2004-07-29) [i386-freebsd4] > > Abort (core dumped) > > i rebuilt the ports index by going to /usr/ports and doing make index, > but i still get this same deal. > > whats up? It helps if you read /usr/ports/UPDATING first :). Kent ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: segmentation fault
On Sat, Nov 20, 2004 at 02:39:50PM -0500, Steel City Phantom wrote: > i am trying to run a portupgrade and have a problem. portupgrade says i > have a stale dependency and need to fix it with pkgdb, when i run that, > i get this > > guinness# pkgdb -F > ---> Checking the package registry database > Stale dependency: php4-4.3.5_7 -> apache-1.3.29_3 (www/apache13): > [Failed `Inappropriate file type or format'] [Updating the portsdb > in /usr/ports ... - 11973 port entries found > .1000.2000.3000.4000.5000/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:587: > > [BUG] Segmentation fault > ruby 1.8.2 (2004-07-29) [i386-freebsd4] > > Abort (core dumped) > > i rebuilt the ports index by going to /usr/ports and doing make index, > but i still get this same deal. > > whats up? You need to get into the habit of 1) Searching the archives before asking questions 2) Reading /usr/ports/UPDATING after every cvsup. Kris pgpgEfs7gYNnM.pgp Description: PGP signature
ldconfig Segmentation fault
Hi, I've done a network installation using the floppies and ftp access through http proxy (the only way to access the net or me), and I have a big problem. I saw, in the installation fase, a lot of Segmentation fault, core dump for ldconfig, after each package installation, but I didn't take them into account, because I knew that I can run ldconfig any time. But after rebooting my station, The ldconfig still gives Segmentation fault. It is the right one, /sbin/ldconfig, not the linux's one (I don't have linux_compat enable yet). Is there any way to repair this installation, or I need to reinstall all? thanks for any help. -- __V__ Ciprian Badescu A L C A T E L Mobile Networks Division R&D Center Phone: +40 56 303100 (ext. 5786) Fax: +40 56 295386 Email: [EMAIL PROTECTED] On Wed, 19 Feb 2003, Hermanto wrote: > Date: Wed, 19 Feb 2003 13:41:06 + > From: Hermanto <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: mplayer with gui > > i want to install mplayer with gui enable. how do i? > does pkg_add has an option for that? > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
midori > preferences > segmentation fault
midori > Edit > Preferences results, nearly every time, in: *** NSPlugin Viewer *** ERROR: rpc_end_sync called when not in sync! Segmentation fault (core dumped) This occurs since 9.1-RELEASE. All ports (midori, linux-f10-flashplugin11, nspluginwrapper, etc) are up to date. No problem with chromium. Haven't tried firefox this time. Compile time for chromium is about 6 hours. As far as I remember, firefox compile time takes even longer. What is wrong with midori ? Thank you in advance, Harald ___ 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: tar segmentation fault
Sorry. left off some information that might come in handy! me$ uname -srm FreeBSD 6.0-STABLE i386 me$ pkg_info | grep tar gtar-1.15.1_1 GNU version of the traditional tar archiver startup-notification-0.8_1 Library that supports startup notification spec from freede me$ Thanks, Ben > tar -cLvy -f /usr/home/me/backup/backup.tar.bz2 /usr/home/me/backup/source/ > > When source/usr/home/me/public_html is empty then it runs fine. But when I > put any links in, tar dies with a segmentation fault. > > Has anyone got any ideas why? > > Thanks, > Ben ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: tar segmentation fault
Ben Paley <[EMAIL PROTECTED]> writes: > Sorry. left off some information that might come in handy! > > me$ uname -srm > FreeBSD 6.0-STABLE i386 > me$ pkg_info | grep tar > gtar-1.15.1_1 GNU version of the traditional tar archiver > startup-notification-0.8_1 Library that supports startup notification spec > from freede You're obviously not *using* gnu tar, because you would be getting errors on the -l option if you were. > me$ > > Thanks, > Ben > > > tar -cLvy -f /usr/home/me/backup/backup.tar.bz2 /usr/home/me/backup/source/ > > > > When source/usr/home/me/public_html is empty then it runs fine. But when I > > put any links in, tar dies with a segmentation fault. > > > > Has anyone got any ideas why? No. I can't reproduce the problem here, using the system tar on RELENG_6 (couple of weeks old). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: tar segmentation fault
On Tuesday 21 February 2006 19:12, Lowell Gilbert wrote: > Ben Paley <[EMAIL PROTECTED]> writes: > > Sorry. left off some information that might come in handy! > > > > me$ uname -srm > > FreeBSD 6.0-STABLE i386 > > me$ pkg_info | grep tar > > gtar-1.15.1_1 GNU version of the traditional tar archiver > > startup-notification-0.8_1 Library that supports startup notification > > spec from freede > > You're obviously not *using* gnu tar, because you would be getting > errors on the -l option if you were. Yup, looks like I'm using bsdtar ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: tar segmentation fault
> When source/usr/home/me/public_html is empty then it runs fine. But when I put > any links in, tar dies with a segmentation fault. > > Has anyone got any ideas why? > Yup, looks like I'm using bsdtar Now that you know which tar you're using, :-) time to drag out the standard debugging process for segmentation faults. 1) get the sources 2) compile, adding "-g" 2a) If you get any compiler warnings, fix them and send the diffs to the maintainer. Often fixing the compiler warnings will fix a seg fault. 3) Try it again. If it still seg faults, run it under a debugger and get a stack backtrace. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: tar segmentation fault
> From: Dieter <[EMAIL PROTECTED]> > Subject: Re: tar segmentation fault > To: freebsd-questions@freebsd.org > Message-ID: <[EMAIL PROTECTED]> > Now that you know which tar you're using, :-) > time to drag out the standard debugging process for > segmentation faults. It's come to that, has it? Oh well... thanks very much for your help, I'll be back in touch with more information soon! Thanks again, Ben ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: tar segmentation fault
On Tuesday 21 February 2006 19:12, Lowell Gilbert wrote: > Ben Paley <[EMAIL PROTECTED]> writes: > > me$ pkg_info | grep tar > > gtar-1.15.1_1 GNU version of the traditional tar archiver > You're obviously not *using* gnu tar, because you would be getting > errors on the -l option if you were. Well, I haven't got round to debugging bsdtar (it compiles without warning using 'make' in /usr/src/usr.bin/tar/), but it turns out gtar works fine, using -h instead of -L . Thanks very much to both of you for pointing me towards a solution. Thanks, Ben ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Segmentation fault (11)
At 05:48 PM 7/27/2005, steve lasiter wrote: This is a questions to the group since I'm not sure if it's related to my FreeBSD 5.4 OS or something else. I'm on a Dell Pentium 2.55Ghz with 1 GB Ram. Background: In trying to install oscommerce I have uninstalled my php5 and went to php4. Because of error I've reinstalled Apache 1.3 and Perl5. My database is MySQL 5.02. I believe that 5.x versions of MySQL are still considered to be beta quality at best. It might be a good idea to use 4.1 which is their recommended version. -Glenn The problem: when I attempt to open an index.php file in the oscommerce program I get, in my httpd-error.log [notice] child pid xxx exit signal Segmentation fault(11) All other php related sites are functioning well with no problems. Do you believe this is being caused by the code in the oscommerce program or something FreeBSD is doing? Thanks for input Dean Lasiter __ Yahoo! Mail for Mobile Take Yahoo! Mail with you! Check email on your mobile phone. http://mobile.yahoo.com/learn/mail ___ 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: Segmentation fault (11)
do you have a copy of the core dump? also sometimes when you use php to interpret the page via the shell it leaves a little extra useful info. since it's a fault and not a kernel panic i wouldnt be worried that its freebsd itself fucking things up. this error only comes up when a program accesses a memory location that it wasn't assigned to. "Because of error I've reinstalled Apache 1.3 and Perl5." what was the error and how was php5 compiled? did you uninstall php4 or did you do a FORCE_PKG_REGISTER? when you say that other php sites work fine do you mean that other php scripts work fine on your apache server? I apologize but your info is pretty general. all i can suggest is do a full deinstall clean on apache+php5 and php4 if the memory glitch has to do with its compilation. perhaps if you email the debug log specifics (strace php "webpage.php") we could understand where the program is at when it crashes. -Ben steve lasiter wrote: This is a questions to the group since I'm not sure if it's related to my FreeBSD 5.4 OS or something else. I'm on a Dell Pentium 2.55Ghz with 1 GB Ram. Background: In trying to install oscommerce I have uninstalled my php5 and went to php4. Because of error I've reinstalled Apache 1.3 and Perl5. My database is MySQL 5.02. The problem: when I attempt to open an index.php file in the oscommerce program I get, in my httpd-error.log [notice] child pid xxx exit signal Segmentation fault(11) All other php related sites are functioning well with no problems. Do you believe this is being caused by the code in the oscommerce program or something FreeBSD is doing? Thanks for input Dean Lasiter Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs ___ 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: Segmentation fault (11)
i seem to use mysql 5.02 just fine even with a few unsuggested code tweaking on my leet 366Mhz cyrix based e-machine :-P thats why i was looking toward a different direction. hopefully you'll solve the situation. -Ben steve lasiter wrote: This is a questions to the group since I'm not sure if it's related to my FreeBSD 5.4 OS or something else. I'm on a Dell Pentium 2.55Ghz with 1 GB Ram. Background: In trying to install oscommerce I have uninstalled my php5 and went to php4. Because of error I've reinstalled Apache 1.3 and Perl5. My database is MySQL 5.02. The problem: when I attempt to open an index.php file in the oscommerce program I get, in my httpd-error.log [notice] child pid xxx exit signal Segmentation fault(11) All other php related sites are functioning well with no problems. Do you believe this is being caused by the code in the oscommerce program or something FreeBSD is doing? Thanks for input Dean Lasiter __ Yahoo! Mail for Mobile Take Yahoo! Mail with you! Check email on your mobile phone. http://mobile.yahoo.com/learn/mail ___ 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: portsnap segmentation fault
Hello, On Sat, Sep 17, 2005 at 02:56:11PM -0600 or thereabouts, Pat Maddox wrote: > When I run portsnap update, I get the following error after it > extracts the files: > Building new INDEX files... Segmentation fault (core dumped) > > This is occuring on three different machines, so I'm guessing it's a > problem with portsnap, not my one machine. But they all have similar > configurations, so it could be my setup, I don't know. > > Any ideas what's going on? You are probably correct in your guess. Colin Percival commited fix and update to portsnap (current version is 0.9.5) today, which fixes make index coredumping when encounter a circular dependency is made. So upgrade your portsnap installation and I hope it will solve your problem. Cheers, Martin -- martin hudec * 421 907 303 393 * [EMAIL PROTECTED] * http://www.aeternal.net "Nothing travels faster than the speed of light with the possible exception of bad news, which obeys its own special laws." Douglas Adams, "The Hitchhiker's Guide to the Galaxy" pgpJMzzh6uoAr.pgp Description: PGP signature
Re: portsnap segmentation fault
I just updated it, and now get the error: Building new INDEX files... make_index: Circular dependency loop found: timidity++-2.13.2_1 depends upon itself. Is that a problem with the database file or something? Do I just wait for Colin to fix it? Thanks for the reply. Pat On 9/17/05, martin hudec <[EMAIL PROTECTED]> wrote: > Hello, > > On Sat, Sep 17, 2005 at 02:56:11PM -0600 or thereabouts, Pat Maddox wrote: > > When I run portsnap update, I get the following error after it > > extracts the files: > > Building new INDEX files... Segmentation fault (core dumped) > > > > This is occuring on three different machines, so I'm guessing it's a > > problem with portsnap, not my one machine. But they all have similar > > configurations, so it could be my setup, I don't know. > > > > Any ideas what's going on? > > You are probably correct in your guess. > > Colin Percival commited fix and update to portsnap (current version is > 0.9.5) today, which fixes make index coredumping when encounter a > circular dependency is made. > > So upgrade your portsnap installation and I hope it will solve your > problem. > > Cheers, > Martin > > -- > martin hudec > > >* 421 907 303 393 >* [EMAIL PROTECTED] >* http://www.aeternal.net > > "Nothing travels faster than the speed of light with the possible > exception of bad news, which obeys its own special laws." > >Douglas Adams, "The Hitchhiker's Guide to the Galaxy" > > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portsnap segmentation fault
Pat Maddox wrote: > When I run portsnap update, I get the following error after it > extracts the files: > Building new INDEX files... Segmentation fault (core dumped) > > Any ideas what's going on? There is a bug in versions of portsnap prior to today which causes make_index to core dump when it encounters a cyclic dependency. To make portsnap work properly again, you can either 1. Upgrade your base system to the latest HEAD or RELENG_6 (if you are using portsnap from the base system), 2. Upgrade to the latest version of portsnap (0.9.5) in the ports tree, or 3. Wait until somebody fixes the audio/timidity++ port. Colin Percival ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Nagios-3.0.6 [Segmentation fault]
Hi I'm having a problem with trying to start nagios-3.0.6 with embedded perl. I'm running freebsd 7.1-RELEASE-p2 with perl-5.8.9. when i try to start nagios i get this error. Performing sanity check of nagios configuration: OK Starting nagios. Segmentation fault is this this a known bug ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Apache segmentation fault
On Jan 11, 2012 12:39 PM, "Robert Fitzpatrick" wrote: > > Upgraded php52 to php53 by pkg_delete of php5 and porinstall php52. Then > I had to manually resort back to php52 by pkg_delete and then > portinstall and now getting a seg fault when restarting apache22 on this > FreeBSD 8.1 server. I narrowed it down to not the php module, but the > two ldap modules I have in apache... > > mail# cat httpd.conf|grep ldap > #LoadModule authnz_ldap_module libexec/apache22/mod_authnz_ldap.so > #LoadModule ldap_module libexec/apache22/mod_ldap.so > > With these two lines commented out, apache restarts without the seg > fault. Tried to force pkg_delete on apache and then portinstall to > rebuild these modules, but same issue afterward. The php module loads > without error, but getting download prompts when trying to access php > pages. Not getting any help from messages or httpd-error logs and all > was working before I messed it up. > > My question is what I should try next to try and fix this issue. Should > I force pkg_delete and rebuild all php packages or ldap packages? Or > some other approach? > > Thanks for any help, Robert > > -- > Robert > ___ > 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" hi, you probably need to replace php.ini ... 5.3 barfs with a 5.2 config file... not sure if the pkg thingy would wipe your config. waitman ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Apache segmentation fault
On Jan 11, 2012 12:54 PM, "Waitman Gobble" wrote: > > > On Jan 11, 2012 12:39 PM, "Robert Fitzpatrick" wrote: > > > > Upgraded php52 to php53 by pkg_delete of php5 and porinstall php52. Then > > I had to manually resort back to php52 by pkg_delete and then > > portinstall and now getting a seg fault when restarting apache22 on this > > FreeBSD 8.1 server. I narrowed it down to not the php module, but the > > two ldap modules I have in apache... > > > > mail# cat httpd.conf|grep ldap > > #LoadModule authnz_ldap_module libexec/apache22/mod_authnz_ldap.so > > #LoadModule ldap_module libexec/apache22/mod_ldap.so > > > > With these two lines commented out, apache restarts without the seg > > fault. Tried to force pkg_delete on apache and then portinstall to > > rebuild these modules, but same issue afterward. The php module loads > > without error, but getting download prompts when trying to access php > > pages. Not getting any help from messages or httpd-error logs and all > > was working before I messed it up. > > > > My question is what I should try next to try and fix this issue. Should > > I force pkg_delete and rebuild all php packages or ldap packages? Or > > some other approach? > > > > Thanks for any help, Robert > > > > -- > > Robert > > ___ > > 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" > > hi, you probably need to replace php.ini ... 5.3 barfs with a 5.2 config file... not sure if the pkg thingy would wipe your config. > > waitman sorry, somehow i missed that paragraph about commenting out the other modules... hope i didn't send you on a wild goose chase for nothing. but the behavior you describe sounds like what happens running with a mismatched php.ini... i once tried to narrow down but decided it more productive to start with a fresh ini file. i believe the problem has to do with the session config lines. that and the way it handles cgi variables (see the EPGS section) are the two biggest changes i noticed. anyway you might check if thats the issue easily by renaming php.ini.. it should run without it. (at least 5.2 would havent tried 5.3) if it runs without php.ini then that could be the problem. by the way you are restarting apache after the changes right? also verify that the modules listed in httpd.conf exist in the paths specified... hope that helps! waitman ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Apache segmentation fault
On 1/11/2012 4:39 PM, Waitman Gobble wrote: > sorry, somehow i missed that paragraph about commenting out the other > modules... hope i didn't send you on a wild goose chase for nothing. but > the behavior you describe sounds like what happens running with a > mismatched php.ini... i once tried to narrow down but decided it more > productive to start with a fresh ini file. i believe the problem has to > do with the session config lines. that and the way it handles cgi > variables (see the EPGS section) are the two biggest changes i > noticed. anyway you might check if thats the issue easily by renaming > php.ini.. it should run without it. (at least 5.2 would havent tried 5.3) > if it runs without php.ini then that could be the problem. > by the way you are restarting apache after the changes right? also > verify that the modules listed in httpd.conf exist in the paths specified... > > hope that helps! > > waitman > Thanks for that, found my php.ini was symlink'd to php.ini-recommended, which is now missing. PHP working now, but still no help with the segmentation fault. I have tested my ldap client pkgs and perl-LDAP to work fine, but when I uncomment those modules, I get the fault when restarting apache > mail# pwd > /usr/local/etc > mail# cat apache22/httpd.conf|grep ldap > LoadModule authnz_ldap_module libexec/apache22/mod_authnz_ldap.so > LoadModule ldap_module libexec/apache22/mod_ldap.so > mail# cat apache22/httpd.conf | grep ServerRoot > ServerRoot "/usr/local" > mail# cat apache22/httpd.conf | grep ldap > LoadModule authnz_ldap_module libexec/apache22/mod_authnz_ldap.so > LoadModule ldap_module libexec/apache22/mod_ldap.so > mail# ls -lah /usr/local/libexec/apache22/*ldap* > -rwxr-xr-x 1 root wheel54K Jan 11 12:29 > /usr/local/libexec/apache22/mod_authnz_ldap.so > -rwxr-xr-x 1 root wheel 115K Jan 11 12:29 > /usr/local/libexec/apache22/mod_ldap.so > mail# rc.d/apache22 restart > Performing sanity check on apache22 configuration: > Syntax OK > Segmentation fault (core dumped) If I comment out the two modules shown, it restarts without issue. -- Robert ___ 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: Ettercap segmentation fault....
On Tue, Jul 6, 2010 at 11:21 PM, Axel Barnabas wrote: > Hello, > > I have compiles ettercap from ports without incident. However, when I attempt > to run ettercap in any way, after a short while the program crashes and I am > presented with an error message which is as follows: > > > Ooops ! This shouldn't happen... > Segmentation Fault... > > Please recompile in debug mode, reproduce the bug and send a bugreport > > > I have deinstalled and recompiled to program twice, yielding no results. > Some additional information which may be useful- > > #pkg_info | grep ettercap > ettercap-gtk2-0.7.3_10,1 A network sniffer/interceptor/injector/logger for > switched > > #uname -a > FreeBSD 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC 2009 > r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > > If anyone wishes me to recompile in debug mode, you will have to tell me how; > I am not familiar with the process. > > Axel Try this: Before building the port (if you're starting from scratch), run: Code: # cd /usr/ports/net-mgmt/ettercap # make fetch # make extract In the file "/usr/ports/net-mgmt/ettercap/work/ettercap-NG-0.7.3/src/protocols/ec_tcp.c" on line 119, change the following line from: Code: opt_end = (u_char *)((int)tcp + tcp->off * 4); To: Code: opt_end = (u_char *)(tcp + tcp->off * 4); ...using your favorite text editor. Then, run the typical: Code: # make config # make build # make install After all of that, give the program a run or two, and see if it's working. Let us all know. -Brandon [Refer to FreeBSD Forum Thread: http://forums.freebsd.org/showthread.php?t=15719] ___ 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"
Segmentation fault when free
Hi all
I'm running FreeBSD 7 on i386. I have a C program compiled with gcc 4.2.1
20070719.
Logically my program is:
char *a;
char *b;
char *c;
while (cond)
{
a = f1(); /* malloc() and send a string */
b = f2(); /* malloc() and send a string */
c = (char *) malloc(strlen(a) + strlen(b) + 1);
c[0] = '\0';
strcat(c, a);
strcat(c, b);
free(a);
free(b);
}
When it executes free(b), my program exits with Segmentation fault: 11. The
free(a) executes well.
The problem is with free(b). Even swap free(b) first and free(a) next, it still
crashes at free(b).
If I comment out free() lines, further down the program, first few characters
of one string get dropped when executes a completely unrelated line.
How could I bit more narrow down the problem?
Many thanks in advance.
Kind regards
Unga
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[Fwd: Suhosin Segmentation Fault]
Not much return on freebsd-isp. I try again here on freebsd-questions. Original-Nachricht Betreff: Suhosin Segmentation Fault Datum: Mon, 13 Oct 2008 09:49:09 +0200 Von: Alain Wolf <[EMAIL PROTECTED]> An: [EMAIL PROTECTED] Newsgruppen: gmane.os.freebsd.isp After upgrading FreeBSD from 6.3-p3 to 6.3-p5 on our server, all websites just display a blank page and every HTTP request created a line as follows in the logs: child pid 80326 exit signal Segmentation fault (11) This same problem happened on another server a few months ago after the upgrade from 6.3-p3 to 6.3-p4, but after a rebuild of all FreeBSD ports all went back to normal. However several rebuilds of all ports did not solve the problem on this one. To narrow down the problem: After disabling the PHP module in Apache the problem disappears. Re-enabling PHP, but disabling the Suhosin extension also works fine. The trick found in this forum, to load the Suhosin extension before all other PHP extensions in /usr/local/etc/php/extensions.ini does not help. In fact not loading any extension at all except Suhosin creates the segfault errors. Commenting out our Suhosin settings in php.ini to load it with default values did not help. FreeBSD 6.3-RELEASE-p5 Apache 2.2.9 (DAV/2 mod_python/3.3.1 Python/2.5.2 SVN/1.5.2) PHP Version 5.2.6 Suhosin Patch 0.9.6.2 Suhosin PHP extension 0.9.27 All installed from the ports. PHP (cli) seems to run fine at all times when called from the command-line. Any suggestions? Thanks Alain Wolf, Zurich, Switzerland ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Segmentation fault (core dumped)
Hi to all The server is give this error whenever i want to start apache22. why? regards -- Share now a pigeon's flight Bluebound along the ancient skies, Its women forever hair and mammal, A Mediterranean town may arise If you rip apart a pigeon's heart. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PHP5 segmentation fault
Hello Jeffrey, Jeffrey Lehman pisze: Hello everyone, this is my first post to the list as I am a new FreeBSD user as of last week. I've installed 7.0RC1 amd64 architecture on my poweredge 2950. I'm having issues with apache22 and php5. Here is the process I went through to install both. 1. Installed www/apache22 using 'make install clean' with default config options. 2. Installed lang/php5 using 'make install clean' with default config options plus apache support. Apache seems to be working fine w/o php5 but after I install php5, apache will core dump on restart. PHP5 also seg faults when executing /usr/local/bin/php # /usr/local/bin/php Segmentation fault: 11 (core dumped) Try editing /usr/local/etc/php/extenstions.ini and comment some extensions testing which one is at fault. Usually, it helps to change the order in which they appear to fix this issue. Been there, done that. HTH Zbigniew Szalbot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: tor, segmentation fault.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 dima wrote: > Hello. > > Does anybody there have experience how to run an ports/security/tor ? > I have use FreeBSD 4.11-RELEASE-p13 and "tor" here always exit with > signal 11 and Segmentation fault message. > > -- > dima <7509107*mail,ru> <2:550/112> Could you provide your make.conf settings, in particular your CFLAGS, CXXFLAGS, and CPUTYPE, or maybe the custom settings in your ports config file(s), etc? Thanks, - -Garrett -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.1 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFkzUWEnKyINQw/HARAokYAJ4qaAYaCw+a78QPGoK9vhauKYDpoACfURZF cV8ED6Vb4XGrTnfJ7ShJC+s= =dMgT -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: tor, segmentation fault.
On Wed, 27 Dec 2006, Garrett Cooper wrote: > > Does anybody there have experience how to run an > > ports/security/tor ? I have use FreeBSD 4.11-RELEASE-p13 and "tor" > > here always exit with signal 11 and Segmentation fault message. > Could you provide your make.conf settings, in particular your > CFLAGS, CXXFLAGS, and CPUTYPE, or maybe the custom settings in your > ports config file(s), etc? cat make.conf | grep ... #NO_CPU_CFLAGS= true# Don't add -march= to CFLAGS automatically #CFLAGS= -O -pipe BDECFLAGS= -W -Wall -ansi -pedantic -Wbad-function-cast -Wcast-align \ -Wcast-qual -Wchar-subscripts -Winline \ -Wmissing-prototypes -Wnested-externs -Wpointer-arith \ -Wredundant-decls -Wshadow -Wstrict-prototypes -Wwrite-strings #SENDMAIL_CFLAGS= CPUTYPE=i686 #CXXFLAGS+= -fmemoize-lookups -fsave-memoized Ports config? Where is it? -- dima <7509107*mail,ru> <2:550/112> ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: tor, segmentation fault.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 dima wrote: > On Wed, 27 Dec 2006, Garrett Cooper wrote: > >>> Does anybody there have experience how to run an >>> ports/security/tor ? I have use FreeBSD 4.11-RELEASE-p13 and "tor" >>> here always exit with signal 11 and Segmentation fault message. > >> Could you provide your make.conf settings, in particular your >> CFLAGS, CXXFLAGS, and CPUTYPE, or maybe the custom settings in your >> ports config file(s), etc? > > cat make.conf | grep ... > #NO_CPU_CFLAGS= true# Don't add -march= to CFLAGS automatically > #CFLAGS= -O -pipe > BDECFLAGS= -W -Wall -ansi -pedantic -Wbad-function-cast -Wcast-align \ >-Wcast-qual -Wchar-subscripts -Winline \ >-Wmissing-prototypes -Wnested-externs -Wpointer-arith \ >-Wredundant-decls -Wshadow -Wstrict-prototypes -Wwrite-strings > #SENDMAIL_CFLAGS= > CPUTYPE=i686 > #CXXFLAGS+= -fmemoize-lookups -fsave-memoized > > Ports config? Where is it? > > -- > dima <7509107*mail,ru> <2:550/112> Hmmm... doesn't look like you have any bad options.. You should try compiling the port with the debug flag (-g) and see if you can point out where it core dumps and then reply with that info or transfer that information on to the maintainer. - -Garrett -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.1 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFk21gEnKyINQw/HARArBIAKCOaDqo5tvRux3vVqVl6LchkoHmzwCgkRs6 i50oU2uX1DdMl2BvTKfsnOA= =ztQZ -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: tor, segmentation fault.
On Wed, 27 Dec 2006, Garrett Cooper wrote: > >>> ports/security/tor ? I have use FreeBSD 4.11-RELEASE-p13 and > >>> "tor" here always exit with signal 11 and Segmentation fault > >>> message. > Hmmm... doesn't look like you have any bad options.. You should try > compiling the port with the debug flag (-g) and see if you can point > out where it core dumps and then reply with that info or transfer > that information on to the maintainer. GDB back trace outputs should be bot enough? I asume the "-g" (debug flag) is a argument. But "make" does not have such arg. Where I should add the "-g" arg to? -- dima <7509107*mail,ru> <2:550/112> ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
phpMyAdmin httpd segmentation fault
I installed FreeBSD 6.2-RELEASE, php-5.1.6_3, php5-extensions-1.0,
mysql-5.0.27 and apache_1.3.37_1.
php -i now works Ok after I moved recode.so to the top of the list
of extensions in extensions.ini. It took a while to figure that
one out. Before that php -i would seg fault and core dump. It
took some google searching and using gdb on the core file to fix
it.
A test web page for phpinfo works fine too. Mysql works OK from
the command line.
However I can't get phpMyAdmin to work. It seg faults in reading
/usr/local/www/phpMyAdmin/libraries/url_generating.lib.php
There is no core dump produced.
I ran ktrace httpd -X
Then when I try to open the phpMyAdmin/index.php page in a browser
httpd seg faults.
Here is the tail of kdump from the ktrace.out from the above ktrace.
1372 httpdCALL gettimeofday(0xbfbf7158,0)
1372 httpdRET gettimeofday 0
1372 httpdCALL lstat(0xbfbf75b0,0xbfbf70f0)
1372 httpdNAMI "/usr"
1372 httpdRET lstat 0
1372 httpdCALL lstat(0xbfbf75b0,0xbfbf70f0)
1372 httpdNAMI "/usr/local"
1372 httpdRET lstat 0
1372 httpdCALL lstat(0xbfbf75b0,0xbfbf70f0)
1372 httpdNAMI "/usr/local/www"
1372 httpdRET lstat 0
1372 httpdCALL lstat(0xbfbf75b0,0xbfbf70f0)
1372 httpdNAMI "/usr/local/www/phpMyAdmin"
1372 httpdRET lstat 0
1372 httpdCALL lstat(0xbfbf75b0,0xbfbf70f0)
1372 httpdNAMI "/usr/local/www/phpMyAdmin/libraries"
1372 httpdRET lstat 0
1372 httpdCALL lstat(0xbfbf75b0,0xbfbf70f0)
1372 httpdNAMI
"/usr/local/www/phpMyAdmin/libraries/url_generating.lib.php"
1372 httpdRET lstat 0
1372 httpdCALL open(0x845eda8,0,0x1b6)
1372 httpdNAMI
"/usr/local/www/phpMyAdmin/libraries/url_generating.lib.php"
1372 httpdRET open 4
1372 httpdCALL fstat(0x4,0x8102748)
1372 httpdRET fstat 0
1372 httpdCALL lseek(0x4,0,0,0,0x1)
1372 httpdRET lseek 0
1372 httpdCALL read(0x4,0x82e3028,0x2000)
1372 httpdGIO fd 4 read 4096 bytes
" $val) {
$return .= $spaces . '' . "\\n";
}
return $return;
}
/**
* Generates text with URL parameters.
*
*
* // note the ?
* echo 'script.php?' . PMA_generate_common_url('mysql', 'rights');
* // produces with cookies enabled:
* // script.php?db=mysql&table=rights
* // with cookies disabled:
* //
script.php?server=1&lang=en-utf-8&db=mysql&table=rights
*
* $params['myparam'] = 'myvalue';
* $params['db'] = 'mysql';
* $params['table'] = 'rights';
* // note the missing ?
* echo 'script.php' . PMA_generate_common_url($params);
* // produces with cookies enabled:
* // script.php?myparam=myvalue&db=mysql&table=rights
* // with cookies disabled:
* //
script.php?server=1&lang=en-utf-8&myparam=myvalue&db=mysql&table=rights
*
* // note the missing ?
* echo 'script.php' . PMA_generate_common_url();
* // produces with cookies enabled:
* // script.php
* // with cookies disabled:
* // script.php?server=1&lang=en-utf-8
*
*
* @param mixedassoc. array with url params or optional string
with database name
* if first param is an array there is also an ?
prefixed to the url
* @param string optional table name only if first param is array
* @param string character to use instead of '&' for deviding
* multiple URL parameters from each other
*
* @return string string with URL parameters
*
* @global string the current language
* @global string the current conversion charset
* @global string the current connection collation
* @global string the current server
* @global arra"
1372 httpdRET read 6467/0x1943
1372 httpdCALL read(0x4,0x82e3028,0x2000)
1372 httpdGIO fd 4 read 0 bytes
""
1372 httpdRET read 0
1372 httpdCALL read(0x4,0x82e3028,0x2000)
1372 httpdGIO fd 4 read 0 bytes
""
1372 httpdRET read 0
1372 httpdCALL close(0x4)
1372 httpdRET close 0
1372 httpdPSIG SIGSEGV SIG_DFL
I moved url_generating.lib.php to url_generating.lib.php.sav and
copied url_generating.lib.php.sav to a new url_generating.lib.php.
Same thing happens.
I tried the latest phpMyAdmin-2.9.2 and it does the exact same thing.
It always seg faults in the exact
nvidia-driver segmentation fault
To celebrate te Xorg upgrade I got rid of all ports installed in my system, then did a fresh install. No problems building; well, I installed first gnome-lite expecting it would pull the complete xorg meta-port and finally had to install this to get all the stuff, but suppose this is harmless. Now, the sad history: I can run X apps with the nv driver, but the nvidia-driver fails. Typescript [...comments...]: [...using the nv driver...] # X -config xorg.conf.new X Window System Version 7.2.0 Release Date: 22 January 2007 X Protocol Version 11, Revision 0, Release 7.2 Build Operating System: FreeBSD 6.2-STABLE i386 Current Operating System: FreeBSD asinusaureus 6.2-STABLE FreeBSD 6.2-STABLE #0: Thu May 24 11:20:28 CEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ZORN i386 Build Date: 21 May 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Thu May 24 11:56:19 2007 (++) Using config file: "/root/xorg.conf.new" (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found) [...works fine; same if I launch the desktop...] [...now as configured with nvidia-xconfig...] # X -config /etc/X11/xorg.conf X Window System Version 7.2.0 Release Date: 22 January 2007 X Protocol Version 11, Revision 0, Release 7.2 Build Operating System: FreeBSD 6.2-STABLE i386 Current Operating System: FreeBSD asinusaureus 6.2-STABLE FreeBSD 6.2-STABLE #0: Thu May 24 11:20:28 CEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ZORN i386 Build Date: 21 May 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Thu May 24 11:57:34 2007 (++) Using config file: "/etc/X11/xorg.conf" [...shows the nvidia splash screen and then aborts...] Fatal server error: Caught signal 11. Server aborting Abort (core dumped) # tail /var/log/messages [...] May 24 11:57:37 asinusaureus kernel: pid 1840 (Xorg), uid 0: exited on signal 6 (core dumped) No relevant info in xorg logs. After much looking, I am still clueless. Any hint? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Segmentation fault & Apache-2.2.9
I continue to see varying amounts of chatter in the 'httpd-error.log' file. This is a snipped of what is being written to the file. ** [Wed Sep 03 06:59:31 2008] [notice] Digest: generating secret for digest authentication ... [Wed Sep 03 06:59:31 2008] [notice] Digest: done [Wed Sep 03 06:59:32 2008] [notice] Apache/2.2.9 (FreeBSD) mod_ssl/2.2.9 OpenSSL/0.9.7e-p1 DAV/2 PHP/5.2.6 with Suhosin-Patch configured -- resuming normal operations [Wed Sep 03 08:28:11 2008] [notice] child pid 1039 exit signal Segmentation fault (11) [Wed Sep 03 08:56:01 2008] [notice] child pid 989 exit signal Segmentation fault (11) [Wed Sep 03 09:29:00 2008] [notice] child pid 1692 exit signal Segmentation fault (11) [Wed Sep 03 09:29:31 2008] [notice] child pid 990 exit signal Segmentation fault (11) ** Some days there may be twenty or more 'segmentation fault' messages. How can I debug this to see what is crashing and why? Everything appears to be operating correctly. -- Gerard [EMAIL PROTECTED] All men profess honesty as long as they can. To believe all men honest would be folly. To believe none so is something worse. John Quincy Adams signature.asc Description: PGP signature
Segmentation fault with smbpasswd
I'm running FreeBSD 6.1-RELEASE and installed samba-3.0.22,1 from a relatively recent snapshot or /usr/ports. Here is the global section of my /usr/local/etc/smb.conf: [global] workgroup = OFFICE server string = Samba Server passdb backend = tdbsam logon script = scripts\logon.bat logon path = \\%L\Profiles\%U logon drive = H: logon home = \\%L\%U domain logons = Yes os level = 35 preferred master = Yes domain master = Yes After a fresh install of samba smbpasswd gives this: [EMAIL PROTECTED] ~]# smbpasswd -a admin New SMB password: Retype new SMB password: Unable to open/create TDB passwd Unable to open/create TDB passwd pdb_getsampwnam: TDB passwd (/usr/local/private/passdb.tdb) did not exist. File successfully created. Segmentation fault: 11 (core dumped) Then it gives this: [EMAIL PROTECTED] ~]# smbpasswd -a admin New SMB password: Retype new SMB password: Unable to open/create TDB passwd pdb_getsampwnam: Unable to open TDB passwd (/usr/local/private/passdb.tdb)! account_policy_get: tdb_fetch_uint32 failed for field 1 (min password length), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 2 (password history), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 3 (user must logon to change password), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 4 (maximum password age), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 5 (minimum password age), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 6 (lockout duration), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 7 (reset count minutes), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 8 (bad lockout attempt), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 9 (disconnect time), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 10 (refuse machine password change), returning 0 TDBSAM version too old (0), trying to convert it. TDBSAM converted successfully. Added user admin. After that, samba seems to work properly. If I touch /usr/local/private/passdb.tdb after a fresh install of samba I have directly the second behavior (no segfault) and then again samba is operational. What did I miss? Regards, Thierry. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ruby1.8 segmentation fault
- Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, March 05, 2004 22:11 Subject: ruby1.8 segmentation fault > Hi BSDers, I read the ports/UPDATING about ruby stuff and do accordingly, > after reinstall portupgrade, I did "portupgrade -fr > /usr/ports/land/ruby16" and here it goes: > > [Updating the pkgdb in /var/db/pkg ... - 435 packages > found (-22 +61) (...)/usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:467: [BUG] > Segmentation fault > ruby 1.8.1 (2003-12-25) [i386-freebsd4] > > Abort (core dumped) > > dont' have the balls the mess with this stuff, so...any idea? > > > Eureka! > > Best regards > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" Hello, There is a problem with portupgrade. See http://freebsd.kde.org for the solution that worked for me. HTH, Steve ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ruby1.8 segmentation fault
[EMAIL PROTECTED] wrote: Hi BSDers, I read the ports/UPDATING about ruby stuff and do accordingly, after reinstall portupgrade, I did "portupgrade -fr /usr/ports/land/ruby16" and here it goes: [Updating the pkgdb in /var/db/pkg ... - 435 packages found (-22 +61) (...)/usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:467: [BUG] Segmentation fault ruby 1.8.1 (2003-12-25) [i386-freebsd4] Abort (core dumped) dont' have the balls the mess with this stuff, so...any idea? I assume you did the first step in UPDATING and did the pkg_delete step, right? If so, you might try fixing up your package database, with pkgdb -F. -- Jonathan Arnold (mailto:[EMAIL PROTECTED]) Daemon Dancing in the Dark, a FreeBSD weblog: http://freebsd.amazingdev.com/blog/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: segmentation fault - jdk4
I have been experiecing similar problems with 5.2.1. I noticed when compiling gnome2, which depends on a *lot* of other packages, gcc simply segfaults a lot. To solve it I just started compiling again, and the gcc would seg fault again. I continued typing make install a looot of time until everything was compiled. However when I compiled smaller projects like pico, bash etc., I had no problems. Maybe there is some kind of memory leek in the gcc 3.3 version on fbsd 5.2.1? I don't think I have a hardware problem either. Right now I am installing 4.9 on the box, since I found the gcc segfault behaviour unacceptable. I hope I wont experience the same kind of problems again... Cheers, -- Michael Birkmose On Sat, 6 Mar 2004, Ricardo Britto wrote: > Hi, > > I'm running 5.2.1 Release version of FreeBSD, gcc 3.3.3 and I'm > getting the same error when trying to compile JDK 1.4 from ports: > > *any_file_that_changes.c or .h*: *number_that_changes*: compiler > error: segmentation fault > > > I've searched for information and people say that could be problems > with gcc or hardware (memory for eg.). I tried to install new version > of gcc (3.4.0) and still continues using the older (3.3.3), tried the > 3.2 and the error continues. > > About the hardware...everything seems to be fine. > Do you have any suggestions? > people through net didn't find any reasonable cause. > > I appreciate your attention, > > Best regards, > > Ricardo > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: time() segmentation fault
At 09:24 PM 3/21/2004, Abel Navarro wrote:
Hi all,
this program ends with a segmentation fault in a FreeBSD 5.1.2-RELEASE:
main() { time(); }
Good for it! Seeing as time takes a pointer to a time_t, not passing it one
would use what ever happened to be on the stack as a pointer.
I don't have made important changes to the release except cosmetic ones. I'm
running the Linux compatibility module and have compiled with gcc 3.3.3. Any
ideas are welcome.
Change it to
main() { time(0); }
And tell us if it crashes then.
--Chuck
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: time() segmentation fault
Oops, you were rigth. I don't believe I have made such a mistake.
Thank you
Abel
On Mon, 22 Mar 2004 16:54, Chuck McManis wrote:
> At 09:24 PM 3/21/2004, Abel Navarro wrote:
> >Hi all,
> >this program ends with a segmentation fault in a FreeBSD 5.1.2-RELEASE:
> >
> >main() { time(); }
>
> Good for it! Seeing as time takes a pointer to a time_t, not passing it one
> would use what ever happened to be on the stack as a pointer.
>
> >I don't have made important changes to the release except cosmetic ones.
> > I'm running the Linux compatibility module and have compiled with gcc
> > 3.3.3. Any ideas are welcome.
>
> Change it to
> main() { time(0); }
>
> And tell us if it crashes then.
>
> --Chuck
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Limewire Port - Segmentation Fault
I'm running FreeBSD 5.2.1 with X11 (KDE) and just did a "make install distclean" for the limewire port in console. Afterward, I typed "exit" to drop down from root to my local account. Then I typed, "limewire" and got this: bash-2.05b$ limewire Segmentation fault bash-2.05b$ Any ideas/suggestions/similar limewire experience or recommendation for another p2p port? TIA -- www.aekelly.com | www.osvdb.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
portsdb -Uu Segmentation fault
Hello, This is on a Pentium-II running FreeBSD 4.10R, portupgrade-20040701_3, ruby-1.8.2.p2_1, and ruby18-bdb1-0.2.2. Here is what I did: $ pkgdb -F $ cvsup ports-supfile $ portsdb -Uu And here is the output I get from portsdb: Updating the ports index ... Generating INDEX.tmp - please wait.. Done. done [Updating the portsdb in /usr/ports ... - 11939 port entries found .1000.2000.3000.4000.5000 .6000.7000.8000../usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:587: [BUG] Segmentation fault ruby 1.8.2 (2004-07-29) [i386-freebsd4] Abort trap (core dumped) I did a google search, and found a bunch of people had a similar problem (Bus Error, not Segmentation fault) in early September, but I didn't notice what (portupgrade/ruby/the ports tree) was actually the problem. What really stumps me is that I have 2 other servers that have the same version of FreeBSD, Ruby and Portupgrade installed that work fine. Any help would be much appreciated. Thank You, Tabor Kelly ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Recompiling `world` throws Segmentation fault
Hi: I updated my source code to 4.10 and went to recompile world using `make buildworld` and it prints this out: gzip -cn /usr/src/usr.sbin/pccard/pccardd/pccard.conf.5 > pccard.conf.5.gz gzip -cn /usr/src/usr.sbin/pccard/pccardd/pccardd.8 > pccardd.8.gz Segmentation fault (core dumped) *** Error code 139 Stop in /usr/src/usr.sbin/pccard. *** Error code 1 Stop in /usr/src/usr.sbin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. 35218# Could someone tell me how to fix this? -- robg [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Apache gives a Segmentation fault
Hi I have some troubles with apache22 When I run phpinfo() I get a Segmentation fault (11) apache-2.2.0_7 php5-5.1.2_1 php5-bz2-5.1.2_1 php5-calendar-5.1.2_1 php5-ctype-5.1.2_1 php5-dom-5.1.2_1 php5-filepro-5.1.2_1 php5-ftp-5.1.2_1 php5-gd-5.1.2_1 php5-gettext-5.1.2_1 php5-iconv-5.1.2_1 php5-imap-5.1.2_1 php5-ldap-5.1.2_1 php5-mbstring-5.1.2_1 php5-mcrypt-5.1.2_1 php5-mhash-5.1.2_1 php5-ming-5.1.2_1 php5-mysql-5.1.2_1 php5-mysqli-5.1.2_1 php5-openssl-5.1.2_1 php5-pcre-5.1.2_1 php5-posix-5.1.2_1 php5-pspell-5.1.2_1 php5-session-5.1.2_1 php5-simplexml-5.1.2_1 php5-sockets-5.1.2_1 php5-tidy-5.1.2_1 php5-xml-5.1.2_1 php5-xmlreader-5.1.2_1 php5-xmlwriter-5.1.2_1 php5-zlib-5.1.2_1 # uname -a FreeBSD scurvy.violetlan.net 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #2: Wed Mar 29 21:01:05 CEST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 I get this in the http-error.log [Fri Apr 14 14:46:34 2006] [notice] child pid 51241 exit signal Segmentation fault (11) When you open http://www.violetlan.net/phpinfo.php it only loads half the page. I have install phpMyAdmin, postfixadmin and squirrelmail-devel and they are all working with no problems. The http.conf is the default from the installation and I have in my /etc/rc.conf apache22_enable="YES" apache22_http_accept_enable="YES" and in my /boot/loader.conf accf_http_load="yes" I made some changes to my /usr/local/etc/apache22/extra/httpd-default.conf where I increased the timeout to 600 MaxKeepAliveRequests to 500 and KeepAliveTimeout to 15 Please help me to find and fix this problem Thanks -- Reinhold Platzoeder [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.violetlan.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Segmentation fault when building kdelibs
I'm trying to upgrade my system, and the build of kdelibs always fails because of some segmentation fault. I have absolutely no idea what all this means, so I'll try to post as much of the error as I can determine is relevant. Hopefully somebody can help me out. In file included from kjanuswidget.cpp:24: /usr/X11R6/include/qheader.h:207: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html> for instructions. gmake[3]: *** [kjanuswidget.lo] Error 1 gmake[3]: Leaving directory `/usr/ports/x11/kdelibs3/work/kdelibs-3.4.2/kdeui' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/x11/kdelibs3/work/kdelibs-3.4.2/kdeui' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/x11/kdelibs3/work/kdelibs-3.4.2' gmake: *** [all] Error 2 *** Error code 2 Stop in /usr/ports/x11/kdelibs3. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade31298.0 make ** Fix the problem and try again. ** Listing the failed packages (*:skipped / !:failed) ! x11/kdelibs3 (kdelibs-3.4.0_1)(segmentation fault) ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Nagios-3.0.6 [Segmentation fault]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Isaac Mabapa said the following on 30.01.2009 12:04: > Hi > > I'm having a problem with trying to start nagios-3.0.6 with embedded perl. > I'm running freebsd 7.1-RELEASE-p2 with perl-5.8.9. > when i try to start nagios i get this error. > > Performing sanity check of nagios configuration: OK > Starting nagios. > Segmentation fault > > is this this a known bug ? Hi. This bug was recently discussed in freebsd-ports. http://www.freebsd.org/cgi/getmsg.cgi?fetch=524413+527152+/usr/local/www/db/text/2009/freebsd-ports/20090125.freebsd-ports - -- Regards, Bogdan Potishuk - --- KeyID: 0x84B8D5142569D30B Fingerprint: 78FC 5C40 07CC D331 148E CC79 84B8 D514 2569 D30B Keyserver: keyserver.pgp.com - --- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREKAAYFAkmEPgoACgkQhLjVFCVp0wtrvgCg+d5AQVPVgUjTqSafQCYgFpWt AjMAn0abbBgUzpMmCvXyNu7JbLglLKLC =1RTw -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Ldapadd Crashed with Segmentation Fault
Hi, I was playing with OpenLDAP installed on FreeBSD 7.1-RELEASE installed through the port system. The configuration file /usr/local/etc/slapd.conf was edited: ... databasebdb #suffix "dc=my-domain,dc=com" #rootdn "cn=Manager,dc=my-domain,dc=com" suffix "dc=example,dc=com" rootdn "cn=Manager,dc=example,dc=com" ... I created a test LDIF file named test1.ldif: dn: dc=example,dc=com objectclass: dcObject objectclass: organization o: Example Company dc: example dn: cn=Manager,dc=example,dc=com objectClass: organizationalRole cn: Manager Then I used ldapadd to add the new entries in the LDIF file: # ldapadd -x -D "cn=Manager,dc=example,dc=com" -W -f test1.ldif Enter LDAP Password: adding new entry "dc=example,dc=com" adding new entry "cn=Manager,dc=example,dc=com" Segmentation fault: 11 (core dumped) Any idea what went wrong? Hong ___ 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"
Segmentation fault: 11 (core dumped)
r...@mx1 ~ 496$ csh Segmentation fault: 11 (core dumped) r...@mx1 ~ 497$ i even updated all my system to latest -RELEASE r...@mx1 ~ 499$ uname -a FreeBSD mx1.alexus.biz 7.1-RELEASE-p4 FreeBSD 7.1-RELEASE-p4 #3: Sun Mar 29 05:42:35 UTC 2009 ale...@dd.alexus.org:/usr/obj/usr/src/sys/GENERIC amd64 r...@mx1 ~ 500$ I've had that on other systems as well, this isn't the first one I'm having this issue... -- http://alexus.org/ ___ 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"
dtrace/userland causing segmentation fault
hello freebsd gurus...
i'm currently using FreeBSD 9.0-CURRENT-201101...
dtrace is enable and working
[root@ ~]# dtrace -l | tail -5
41473profile tick-1000
41474profile tick-5000
41475profile tick-1sec
41476 database5533db main
query-done
41477 database5533db main
query-start
i´m trying to use dtrace with a very basic userland program and i´m
100% of the time getting segmentation faults...
-- probes definition file --
[root@ ~]# cat simple_probes.d
provider simple {
probe loop(int);
};
-- simple program --
[root@ ~]# cat simple.c
#include
#include "simple_probes.h"
int main() {
int i;
i=0;
while(1) {
printf("%d\n",i);
i++;
SIMPLE_LOOP(i);
}
return(0);
}
-- the steps i use to get the program compiled are --
[root@ ~]# dtrace -C -h -s simple_probes.d
[root@ ~]# gcc -c simple.c
[root@ ~]# dtrace -G -s simple_probes.d simple.o
[root@ ~]# gcc -lelf -o simple simple_probes.o simple.o
-- but when i run the program i always get segmentation fault >:( --
[root@ ~]# ./simple
0
Segmentation fault: 11 (core dumped)
i´ve been banging my head against a wall trying to troubleshoot this
issue with obviously no success...
have any of the freebsd gurus found a similar behavior in the past
regarding userland dtrace?
any pointers/links/words of encouragement will be greatly appreciated...
regards,
javier
___
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"
pyglet font load segmentation fault
Dear all,
I posted about this problem a few months ago and have been scouring
the web ever since but I cannot find the slightest hint at a solution.
Actually, it seems that nobody else has reported a similar problem,
which I find really weird since the function is such a basic one in
pyglet -- quoting Zoolander, "I feel like I am taking crazy pills!"
The problem is that I cannot use the pyglet.font.load() function at
all without causing a segmentation fault:
python
import pyglet
arial = pyglet.font.load('Arial')
Segmentation fault
My system is running FreeBSD 8.1/amd64 with an Nvidia GeForce 9500GT
and the latest driver from Nvidia (256.53), and with all the ports
up-to-date as of today.
python26-2.6.5_1 was compiled with standard options:
WITH_THREADS=true
WITHOUT_HUGE_STACK_SIZE=true
WITHOUT_SEM=true
WITHOUT_PTH=true
WITH_UCS4=true
WITH_PYMALLOC=true
WITH_IPV6=true
WITHOUT_FPECTL=true
Any help would be tremendously appreciated,
thanks in advance
giuseppe
___
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: Segmentation fault when free
--- On Fri, 9/19/08, Unga <[EMAIL PROTECTED]> wrote:
> From: Unga <[EMAIL PROTECTED]>
> Subject: Segmentation fault when free
> To: freebsd-questions@freebsd.org
> Date: Friday, September 19, 2008, 9:17 AM
> Hi all
>
> I'm running FreeBSD 7 on i386. I have a C program
> compiled with gcc 4.2.1 20070719.
>
> Logically my program is:
>
> char *a;
> char *b;
> char *c;
>
> while (cond)
> {
> a = f1(); /* malloc() and send a string */
> b = f2(); /* malloc() and send a string */
>
> c = (char *) malloc(strlen(a) + strlen(b) + 1);
> c[0] = '\0';
>
> strcat(c, a);
> strcat(c, b);
>
> free(a);
> free(b);
> }
>
> When it executes free(b), my program exits with
> Segmentation fault: 11. The free(a) executes well.
>
> The problem is with free(b). Even swap free(b) first and
> free(a) next, it still crashes at free(b).
>
> If I comment out free() lines, further down the program,
> first few characters of one string get dropped when executes
> a completely unrelated line.
>
> How could I bit more narrow down the problem?
>
> Many thanks in advance.
>
> Kind regards
> Unga
>
>
im affraid i didnt implement your request correctly but the program below did
not crash my server under root in 60 seconds
#include
#include
#include
char *a;
char *b;
char *c;
char *abd = "Hi, im a string 1\0";
char *bbd = "Hey, im a string 2\0";
char *f1(void){
char *ab;
ab = malloc(strlen (abd));
memcpy(ab, abd, strlen(abd));
printf("f1(): %s\n", ab);
return ab;
}
char *f2(void){
char *bb;
bb = malloc(strlen (bbd));
memcpy(bb, bbd, strlen(bbd));
printf("f1(): %s\n", bb);
return bb;
}
int
main(void)
{
while (1)
{
a = f1(); /* malloc() and send a string */
b = f2(); /* malloc() and send a string */
c = (char *) malloc(strlen(a) + strlen(b) + 1);
c[0] = '\0';
strcat(c, a);
strcat(c, b);
free(a);
free(b);
}
}
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Segmentation fault when free
--- On Sat, 9/20/08, Nash Nipples <[EMAIL PROTECTED]> wrote:
> From: Nash Nipples <[EMAIL PROTECTED]>
> Subject: Re: Segmentation fault when free
> To: freebsd-questions@freebsd.org
> Date: Saturday, September 20, 2008, 4:14 AM
> --- On Fri, 9/19/08, Unga <[EMAIL PROTECTED]> wrote:
>
> > From: Unga <[EMAIL PROTECTED]>
> > Subject: Segmentation fault when free
> > To: freebsd-questions@freebsd.org
> > Date: Friday, September 19, 2008, 9:17 AM
> > Hi all
> >
> > I'm running FreeBSD 7 on i386. I have a C program
> > compiled with gcc 4.2.1 20070719.
> >
> > Logically my program is:
> >
> > char *a;
> > char *b;
> > char *c;
> >
> > while (cond)
> > {
> > a = f1(); /* malloc() and send a string */
> > b = f2(); /* malloc() and send a string */
> >
> > c = (char *) malloc(strlen(a) + strlen(b) + 1);
> > c[0] = '\0';
> >
> > strcat(c, a);
> > strcat(c, b);
> >
> > free(a);
> > free(b);
> > }
> >
> > When it executes free(b), my program exits with
> > Segmentation fault: 11. The free(a) executes well.
> >
> > The problem is with free(b). Even swap free(b) first
> and
> > free(a) next, it still crashes at free(b).
> >
> > If I comment out free() lines, further down the
> program,
> > first few characters of one string get dropped when
> executes
> > a completely unrelated line.
> >
> > How could I bit more narrow down the problem?
> >
> > Many thanks in advance.
> >
> > Kind regards
> > Unga
> >
> >
>
> im affraid i didnt implement your request correctly but the
> program below did not crash my server under root in 60
> seconds
>
> #include
> #include
> #include
>
> char *a;
> char *b;
> char *c;
>
> char *abd = "Hi, im a string 1\0";
> char *bbd = "Hey, im a string 2\0";
>
> char *f1(void){
> char *ab;
> ab = malloc(strlen (abd));
> memcpy(ab, abd, strlen(abd));
> printf("f1(): %s\n", ab);
> return ab;
> }
>
> char *f2(void){
> char *bb;
> bb = malloc(strlen (bbd));
> memcpy(bb, bbd, strlen(bbd));
> printf("f1(): %s\n", bb);
> return bb;
> }
>
> int
> main(void)
> {
>
> while (1)
> {
>
> a = f1(); /* malloc() and send a string */
> b = f2(); /* malloc() and send a string */
>
> c = (char *) malloc(strlen(a) + strlen(b) + 1);
> c[0] = '\0';
>
> strcat(c, a);
> strcat(c, b);
>
> free(a);
> free(b);
> }
> }
>
Hi thank you very much for your reply and the test case.
That is, in a trivial case like this, free() works well. Hopefully free() works
well in all cases too.
But my main program is 1900 lines, f1() and f2() are in a 2200 lines second
file. The f1() and f2() calls some functions from a 500 lines third file. The
main program call another function, f3(), from 2nd file, pass pointers to two
functions f4(), f5() of main program. The while loop iterate more than one
million times. Its quite a complex situation.
There must be an error somewhere else. I noted free() causes lot of troubles.
It is easy to write complex programs if you just let to leak memory. But in my
case, since the program iterate millions of times, if I let to leak, I'm sure
it will run out of RAM.
So the question is, if you were to encounter this issue, how would you approach
it and find the culprit?
I'm using pretty basic tools to write complex programs. I use Kate to write
programs, Makefiles to compile, use GCC, and use ddd in case of a trouble.
Best regards
Unga
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Segmentation fault when free
On Fri, 19 Sep 2008 20:03:03 -0700 (PDT), Unga <[EMAIL PROTECTED]> wrote: > Hi thank you very much for your reply and the test case. > > That is, in a trivial case like this, free() works well. Hopefully > free() works well in all cases too. > > But my main program is 1900 lines, f1() and f2() are in a 2200 lines > second file. The f1() and f2() calls some functions from a 500 lines > third file. The main program call another function, f3(), from 2nd > file, pass pointers to two functions f4(), f5() of main program. The > while loop iterate more than one million times. Its quite a complex > situation. You are probably calling free() multiple times for the same buffer. Try tracing the malloc and free calls, using the information from this message: http://lists.freebsd.org/pipermail/freebsd-questions/2008-July/179480.html > There must be an error somewhere else. I noted free() causes lot of > troubles. It is easy to write complex programs if you just let to leak > memory. But in my case, since the program iterate millions of times, > if I let to leak, I'm sure it will run out of RAM. Leaking memory is *never* a good choice. Especially if you are writing library code that others are supposed to use, or code that is supposed to run millions of times. While it's understandable as a 'quick hack' when you are first writing a program, I've seen far too many 'quick hacks' that lived years and years after the original 'experimental' period passed. Hence the knee-jerk reaction when I see leaks being used as a 'temporary' solution :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Segmentation fault when free
--- On Sat, 9/20/08, Giorgos Keramidas <[EMAIL PROTECTED]> wrote: > From: Giorgos Keramidas <[EMAIL PROTECTED]> > Subject: Re: Segmentation fault when free > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED], freebsd-questions@freebsd.org > Date: Saturday, September 20, 2008, 2:23 PM > On Fri, 19 Sep 2008 20:03:03 -0700 (PDT), Unga > <[EMAIL PROTECTED]> wrote: > > Hi thank you very much for your reply and the test > case. > > > > That is, in a trivial case like this, free() works > well. Hopefully > > free() works well in all cases too. > > > > But my main program is 1900 lines, f1() and f2() are > in a 2200 lines > > second file. The f1() and f2() calls some functions > from a 500 lines > > third file. The main program call another function, > f3(), from 2nd > > file, pass pointers to two functions f4(), f5() of > main program. The > > while loop iterate more than one million times. Its > quite a complex > > situation. > > You are probably calling free() multiple times for the same > buffer. > > Try tracing the malloc and free calls, using the > information from this > message: > > http://lists.freebsd.org/pipermail/freebsd-questions/2008-July/179480.html > > > There must be an error somewhere else. I noted free() > causes lot of > > troubles. It is easy to write complex programs if you > just let to leak > > memory. But in my case, since the program iterate > millions of times, > > if I let to leak, I'm sure it will run out of RAM. > > Leaking memory is *never* a good choice. Especially if you > are writing > library code that others are supposed to use, or code that > is supposed > to run millions of times. > > While it's understandable as a 'quick hack' > when you are first writing a > program, I've seen far too many 'quick hacks' > that lived years and years > after the original 'experimental' period passed. > Hence the knee-jerk > reaction when I see leaks being used as a > 'temporary' solution :) Hi Giorgos, thank you very much for your reply. ktrace.out shows: malloc_init() 0x8103400 = malloc(1024) malloc_init() malloc_init() 0x810b0b0 = malloc(400) : so many malloc : so many free : malloc/free combinations : free(0xbfbfc9c9) 1. This clearly shows my program is trying to free a memory that has not been allocated. How it could have happened? 2. Is it correct to have many malloc_init()? Best regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Segmentation fault when free
On Sat, 20 Sep 2008 00:31:41 -0700 (PDT), Unga <[EMAIL PROTECTED]> wrote:
> --- On Sat, 9/20/08, Giorgos Keramidas <[EMAIL PROTECTED]> wrote:
>> You are probably calling free() multiple times for the same buffer.
>>
>> Try tracing the malloc and free calls, using the information from
>> this message:
>>
>> http://lists.freebsd.org/pipermail/freebsd-questions/2008-July/179480.html
>
> Hi Giorgos, thank you very much for your reply.
You are welcome :)
> ktrace.out shows:
> malloc_init()
> 0x8103400 = malloc(1024)
> malloc_init()
> malloc_init()
> 0x810b0b0 = malloc(400)
> :
> so many malloc
> :
> so many free
> :
> malloc/free combinations
> :
> free(0xbfbfc9c9)
>
> 1. This clearly shows my program is trying to free a memory that has
> not been allocated. How it could have happened?
Aha. This looks remarkably like an address in the runtime stack. It
usually happens when you have a function that returns the address of a
'local' variable, instead of a newly allocated heap area, i.e.:
char *
function(void)
{
char buffer[100];
return buf;
}
> 2. Is it correct to have many malloc_init()?
Yes, that's ok. If your program is threaded, FreeBSD's pthread
implementation calls malloc(3) and malloc_init() takes special care of
initializing the internal malloc state only one time.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Segmentation fault when free
--- On Sat, 9/20/08, Giorgos Keramidas <[EMAIL PROTECTED]> wrote:
> > 1. This clearly shows my program is trying to free a
> memory that has
> > not been allocated. How it could have happened?
>
> Aha. This looks remarkably like an address in the runtime
> stack. It
> usually happens when you have a function that returns the
> address of a
> 'local' variable, instead of a newly allocated heap
> area, i.e.:
>
> char *
> function(void)
> {
> char buffer[100];
>
> return buf;
> }
>
This problem happens very early stage of my program. Its the very first free()
develops a problem.
I checked again, up to the this problematic free(), functions return newly
allocated strings properly:
char *f( )
{
char *newstr = NULL;
:
newstr = (char *) malloc(p - sp + 1);
if (newstr == NULL)
return NULL;
:
return newstr;
}
Can a yet not executed wrong free() elsewhere cause a problem of this nature?
Best regards
Unga
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Segmentation fault when free
> I checked again, up to the this problematic free(),
> functions return newly allocated strings properly:
>
> char *f( )
> {
> char *newstr = NULL;
> :
> newstr = (char *) malloc(p - sp + 1);
> if (newstr == NULL)
> return NULL;
> :
> return newstr;
> }
>
> Can a yet not executed wrong free() elsewhere cause a
> problem of this nature?
>
> Best regards
> Unga
>
i'm sorry i just dont really cant see a problem with free()
can you please explain it in a more simple way?
it really starts to exceed my screen height
#include
#include
#include
char *a;
char *b;
char *c;
char *abd = "Hi, im a string
1\0";
char *bbd = "Hey, im a string 2\0";
char *f(char *d){
char *newstr = NULL; char *p, *sp;
sp = malloc(strlen (d)); memcpy(sp, d, strlen(d));
p = strchr(sp, 44);
newstr = (char *) malloc(p - sp + 1);
if (newstr == NULL){
newstr = malloc(1);
*newstr = '\0';
return newstr; /* you really dont want to return NULL to strlen() */
}
*p = '\0';
memcpy(newstr, sp, sizeof(char) * (p - sp));
return newstr;
}
char *f1(void){
char *ab;
ab = f(abd);
printf("f1(): %s\n", ab);
return ab;
}
char *f2(void){
char *bb;
bb = f(bbd);
printf("f2(): %s\n", bb);
return bb;
}
int
main(void)
{
while (1)
{
a = f1(); /* malloc and send a string */
b = f2(); /* malloc and send a string */
c =
(char *) malloc(strlen(a) + strlen(b) + 1);
c[0] = '\0';
strcat(c, a);
strcat(c, b);
printf("main(): %s\n", c);
free(a);
free(b);
free(c);
}
}
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Segmentation fault when free
actually what i think someone should really tell you is that maybe you should take a look at the free() manual which is available here http://www.freebsd.org/cgi/man.cgi?query=free&apropos=0&sektion=0&manpath=FreeBSD+7.0-RELEASE&format=html or you can try to run `man free` in the console. there is a good explanation on diagnostic and debugging malloc related problems can someone please explain to me what happens to the allocated memory called within a function assigned to its local pointer after this function ends ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Segmentation fault when free
On Saturday 20 September 2008 13:46:23 Nash Nipples wrote: > can someone please explain to me what happens to the allocated memory > called within a function assigned to its local pointer after this function > ends Ok - let's see if I get this right: - the allocated memory - called within a function - assigned to a local pointer Any malloc'ed memory is application global accessible. Assigning a pointer to a variable doesn't allocate memory (the compiler and runtime libraries already setup storage for the variable, at declaration time). So, I have no idea what you mean with the "called within a function" part. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Segmentation fault when free
> > can someone please explain to me what happens to the
> allocated memory
> > called within a function assigned to its local pointer
> after this function
> > ends
>
> Ok - let's see if I get this right:
> - the allocated memory
> - called within a function
> - assigned to a local pointer
>
> Any malloc'ed memory is application global accessible.
> Assigning a pointer to
> a variable doesn't allocate memory (the compiler and
> runtime libraries
> already setup storage for the variable, at declaration
> time). So, I have no
> idea what you mean with the "called within a
> function" part.
>
> --
> Mel
>
thanks for making it even more clear to me.
actually what i meant was this:
void function(void){
char *p;
p = malloc(1);
}
int main(void){
while (1){
function();
/* in the end of this function function()
* the memory is still allocated
* even when the only pointer who knows its address
* does not longer exist
* which is why we have to free() the memory
* during the application runtime
* to avoid it from growing to ridiculous size
*/
}
}
but even if you kill -SEGV `pgrep this` (Segmentation fault (core dumped) the
memory is getting freed anyway (presumably by the glorious kernel). which you
can see dynamicly by typing top in the console.
in other words segmentation fault when free() is not a scary thing here. it is
a matter of style and the way to find own errors. or maybe reading warnings if
you compile with the flags -ansi -pedantic
oh and by the way:
> char *
> function(void)
> {
> char buffer[100];
>
> return buffer;
> }
that is an easier approach because you get warned on passing an address to a
local variable
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Segmentation fault when free
On Sun, 21 Sep 2008 05:57:06 -0700 (PDT), Nash Nipples <[EMAIL PROTECTED]>
wrote:
> thanks for making it even more clear to me.
> actually what i meant was this:
>
> void function(void){
> char *p;
> p = malloc(1);
> }
> int main(void){
> while (1){
> function();
> /* in the end of this function function()
> * the memory is still allocated
> * even when the only pointer who knows its address
> * does not longer exist
> * which is why we have to free() the memory
> * during the application runtime
> * to avoid it from growing to ridiculous size
> */
> }
> }
This won't throw SEGV in free() because, well, it never calls free(),
but it leaks memory like mad :)
> but even if you kill -SEGV `pgrep this` (Segmentation fault (core
> dumped) the memory is getting freed anyway (presumably by the glorious
> kernel). which you can see dynamicly by typing top in the console.
Yes. When a process terminates, the kernel dismantles and releases all
its 'mapped memory areas', including the heap where malloc()'ed memory
comes from.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Segmentation fault when free
On Sunday 21 September 2008 14:57:06 Nash Nipples wrote:
> > > can someone please explain to me what happens to the
> >
> > allocated memory
> >
> > > called within a function assigned to its local pointer
> >
> > after this function
> >
> > > ends
> >
> > Ok - let's see if I get this right:
> > - the allocated memory
> > - called within a function
> > - assigned to a local pointer
> >
> > Any malloc'ed memory is application global accessible.
> > Assigning a pointer to
> > a variable doesn't allocate memory (the compiler and
> > runtime libraries
> > already setup storage for the variable, at declaration
> > time). So, I have no
> > idea what you mean with the "called within a
> > function" part.
> >
> > --
> > Mel
>
> thanks for making it even more clear to me.
> actually what i meant was this:
>
> void function(void){
> char *p;
> p = malloc(1);
> }
> int main(void){
> while (1){
> function();
> /* in the end of this function function()
> * the memory is still allocated
> * even when the only pointer who knows its address
> * does not longer exist
> * which is why we have to free() the memory
> * during the application runtime
> * to avoid it from growing to ridiculous size
> */
> }
> }
Right, this is one of the annoyances of C-programming "Who still knows where
my pointer is". You can use a general rule though:
If I don't return this pointer, and I don't assign this pointer to a
parameter, and I don't assign this pointer to a global variable, I should
free this pointer myself.
(Yes yes, malloc'd static storage - new can of worms).
--
Mel
Problem with today's modular software: they start with the modules
and never get to the software part.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Segmentation fault when free
On Sun, 21 Sep 2008 05:57:06 -0700 (PDT)
Nash Nipples <[EMAIL PROTECTED]> wrote:
> but even if you kill -SEGV `pgrep this` (Segmentation fault (core
> dumped) the memory is getting freed anyway (presumably by the
> glorious kernel). which you can see dynamicly by typing top in the
> console.
The idea that malloc() allocates memory is really a C language
abstraction. What it actually does is allocate a region in the
process's virtual address space. The mapping of physical memory to
virtual address space is handled at a lower-level and doesn't rely on
malloc() or free().
> in other words segmentation fault when free() is not a scary thing
> here. it is a matter of style and the way to find own errors. or
> maybe reading warnings if you compile with the flags -ansi -pedantic
I'm not sure what you are saying here, but the handling of dynamic
memory in C is something that needs to be well thought-out in
advance. Bugs is this area can be very difficult and time-consuming
to track-down.
> oh and by the way:
>
> > char *
> > function(void)
> > {
> > char buffer[100];
> >
> > return buffer;
> > }
>
> that is an easier approach because you get warned on passing an
> address to a local variable
This was an example of how to generate a failure, it's not an approach.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Segmentation fault when free
On Mon, 22 Sep 2008 02:31:57 +0100, RW <[EMAIL PROTECTED]> wrote:
>Nash Nipples <[EMAIL PROTECTED]> wrote:
>>Giorgos Keramidas wrote:
>>> char *
>>> function(void)
>>> {
>>> char buffer[100];
>>>
>>> return buffer;
>>> }
>>
>> that is an easier approach because you get warned on passing an
>> address to a local variable
>
> This was an example of how to generate a failure, it's not an
> approach.
Yes. It was *only* written to illustrate how a particular failure could
happen. I wouldn't recommend this to anyone as a programming approach :)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [Fwd: Suhosin Segmentation Fault]
On Wed, Oct 15, 2008 at 07:25:08PM +0200, Alain Wolf wrote: > Not much return on freebsd-isp. > I try again here on freebsd-questions. > > Original-Nachricht > Betreff: Suhosin Segmentation Fault > Datum: Mon, 13 Oct 2008 09:49:09 +0200 > Von: Alain Wolf <[EMAIL PROTECTED]> > An: [EMAIL PROTECTED] > Newsgruppen: gmane.os.freebsd.isp > > After upgrading FreeBSD from 6.3-p3 to 6.3-p5 on our server, all > websites just display a blank page and every HTTP request created a line > as follows in the logs: > > child pid 80326 exit signal Segmentation fault (11) > > This same problem happened on another server a few months ago after the > upgrade from 6.3-p3 to 6.3-p4, but after a rebuild of all FreeBSD ports > all went back to normal. However several rebuilds of all ports did not > solve the problem on this one. > > To narrow down the problem: After disabling the PHP module in Apache the > problem disappears. > > Re-enabling PHP, but disabling the Suhosin extension also works fine. > > The trick found in this forum, to load the Suhosin extension before all > other PHP extensions in /usr/local/etc/php/extensions.ini does not help. > In fact not loading any extension at all except Suhosin creates the > segfault errors. Suhosin is not an extension you load in extensions.ini; it's a patch applied to the core of PHP. The extension ordering problem, however, has been thoroughly discussed on -ports in the past. It happens to some and not others. There is no guaranteed way to determine what works and what doesn't. You have to literally enable line-by-line until you figure out which one is causing the problem. You can also try building lang/php5 with DEBUG enabled and then when PHP segfaults, run gdb on the coredump and see if you can get a coherent backtrace (sometimes difficult with Apache in the way) to see what sort of functions are causing the crash; often each extension has its own function names, so that might give you some clues. > PHP (cli) seems to run fine at all times when called from the command-line. Now that's very interesting, given as the CLI version also loads all the extensions listed in extensions.ini. Can you post your /usr/local/etc/php/extensions.ini? You didn't list off what extensions you have installed. -- | 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: [Fwd: Suhosin Segmentation Fault]
Jeremy Chadwick wrote: Suhosin is not an extension you load in extensions.ini; it's a patch applied to the core of PHP. % grep suhosin /usr/local/etc/php/extensions.ini extension=suhosin.so It's both a set of patches to the PHP core, and a loadable module. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: [Fwd: Suhosin Segmentation Fault]
On Wed, Oct 15, 2008 at 08:26:09PM +0100, Matthew Seaman wrote: > Jeremy Chadwick wrote: > >> Suhosin is not an extension you load in extensions.ini; it's a patch >> applied to the core of PHP. > > % grep suhosin /usr/local/etc/php/extensions.ini > extension=suhosin.so > > It's both a set of patches to the PHP core, and a loadable module. > > Cheers, > > Matthew Are you sure? # find /usr/local/lib/php -name "*suhosin*" -ls # # grep -i suhosin /var/db/ports/php5/options WITH_SUHOSIN=true # grep -i suhosin /usr/local/etc/php/extensions.ini # # pkg_version -v | grep php5 php5-5.2.6_2= up-to-date with port php5-extensions-1.1 = up-to-date with port php5-mysql-5.2.6_2 = up-to-date with port php5-pcre-5.2.6_2 = up-to-date with port php5-simplexml-5.2.6_2 = up-to-date with port # grep -i php5 /usr/local/etc/apache22/httpd.conf LoadModule php5_modulelibexec/apache22/libphp5.so # php -i | grep -i suhosin This server is protected with the Suhosin Patch 0.9.6.2 suhosin.log.phpscript => 0 => 0 suhosin.log.phpscript.is_safe => Off => Off suhosin.log.phpscript.name => no value => no value suhosin.log.sapi => no value => no value suhosin.log.script => no value => no value suhosin.log.script.name => no value => no value suhosin.log.syslog => no value => no value suhosin.log.syslog.facility => no value => no value suhosin.log.syslog.priority => no value => no value suhosin.log.use-x-forwarded-for => Off => Off :-) -- | 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: [Fwd: Suhosin Segmentation Fault]
On Wed, Oct 15, 2008 at 2:35 PM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote: > On Wed, Oct 15, 2008 at 08:26:09PM +0100, Matthew Seaman wrote: >> Jeremy Chadwick wrote: >> >>> Suhosin is not an extension you load in extensions.ini; it's a patch >>> applied to the core of PHP. >> >> % grep suhosin /usr/local/etc/php/extensions.ini >> extension=suhosin.so >> >> It's both a set of patches to the PHP core, and a loadable module. >> >> Cheers, >> >> Matthew > > Are you sure? Yes - the suhosin extension is located in the ports tree at: /usr/ports/security/php-suhosin Install instructions are at: http://www.hardened-php.net/suhosin/how_to_install_or_upgrade.html#installing_the_extension It's been a while since I've looked at the suhosin options and I can't remember what the differences are between the extension and the core-php patch. Matt > > # find /usr/local/lib/php -name "*suhosin*" -ls > # > > # grep -i suhosin /var/db/ports/php5/options > WITH_SUHOSIN=true > > # grep -i suhosin /usr/local/etc/php/extensions.ini > # > > # pkg_version -v | grep php5 > php5-5.2.6_2= up-to-date with port > php5-extensions-1.1 = up-to-date with port > php5-mysql-5.2.6_2 = up-to-date with port > php5-pcre-5.2.6_2 = up-to-date with port > php5-simplexml-5.2.6_2 = up-to-date with port > > # grep -i php5 /usr/local/etc/apache22/httpd.conf > LoadModule php5_modulelibexec/apache22/libphp5.so > > # php -i | grep -i suhosin > This server is protected with the Suhosin Patch 0.9.6.2 > suhosin.log.phpscript => 0 => 0 > suhosin.log.phpscript.is_safe => Off => Off > suhosin.log.phpscript.name => no value => no value > suhosin.log.sapi => no value => no value > suhosin.log.script => no value => no value > suhosin.log.script.name => no value => no value > suhosin.log.syslog => no value => no value > suhosin.log.syslog.facility => no value => no value > suhosin.log.syslog.priority => no value => no value > suhosin.log.use-x-forwarded-for => Off => Off > > :-) > > -- > | 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: [Fwd: Suhosin Segmentation Fault]
Hi, all-- On Oct 15, 2008, at 12:47 PM, Matt wrote: It's been a while since I've looked at the suhosin options and I can't remember what the differences are between the extension and the core-php patch. If you check the following, they discuss the difference in protection between using just the patch versus the extension: http://www.hardened-php.net/suhosin/why.html http://www.hardened-php.net/suhosin/a_feature_list.html Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [Fwd: Suhosin Segmentation Fault]
On 15.10.2008 20:55, Jeremy Chadwick wrote: > On Wed, Oct 15, 2008 at 07:25:08PM +0200, Alain Wolf wrote: >> Not much return on freebsd-isp. >> I try again here on freebsd-questions. >> >> Original-Nachricht ---- >> Betreff: Suhosin Segmentation Fault >> Datum: Mon, 13 Oct 2008 09:49:09 +0200 >> Von: Alain Wolf <[EMAIL PROTECTED]> >> An: [EMAIL PROTECTED] >> Newsgruppen: gmane.os.freebsd.isp >> >> After upgrading FreeBSD from 6.3-p3 to 6.3-p5 on our server, all >> websites just display a blank page and every HTTP request created a line >> as follows in the logs: >> >> child pid 80326 exit signal Segmentation fault (11) >> >> This same problem happened on another server a few months ago after the >> upgrade from 6.3-p3 to 6.3-p4, but after a rebuild of all FreeBSD ports >> all went back to normal. However several rebuilds of all ports did not >> solve the problem on this one. >> >> To narrow down the problem: After disabling the PHP module in Apache the >> problem disappears. >> >> Re-enabling PHP, but disabling the Suhosin extension also works fine. >> >> The trick found in this forum, to load the Suhosin extension before all >> other PHP extensions in /usr/local/etc/php/extensions.ini does not help. >> In fact not loading any extension at all except Suhosin creates the >> segfault errors. > > Suhosin is not an extension you load in extensions.ini; it's a patch > applied to the core of PHP. Suhosin is *both*. A patch for php and a extension module for PHP. >From http://www.hardened-php.net/suhosin/index.html: Suhosin comes in two independent parts, that can be used separately or in combination. The first part is a small patch against the PHP core, that implements a few low-level protections against bufferoverflows or format string vulnerabilities and the second part is a powerful PHP extension that implements all the other protections. The suhosin patch works fine on our servers. But the extension does not. > > The extension ordering problem, however, has been thoroughly discussed > on -ports in the past. It happens to some and not others. There is no > guaranteed way to determine what works and what doesn't. You have to > literally enable line-by-line until you figure out which one is causing > the problem. I tried enabling and disabling extensions. All of them work, as long as suhosin.so is not loaded. Regardless of the order. If I disable all other extensions and load only suhosin.so in /usr/local/etc/php/extensions.ini the apache processes are still crashing. > > You can also try building lang/php5 with DEBUG enabled and then when PHP > segfaults, run gdb on the coredump and see if you can get a coherent > backtrace (sometimes difficult with Apache in the way) to see what sort > of functions are causing the crash; often each extension has its own > function names, so that might give you some clues. Hard for me, as this disrupts customer services. We are running without the extensions for now. > >> PHP (cli) seems to run fine at all times when called from the command-line. > > Now that's very interesting, given as the CLI version also loads all the > extensions listed in extensions.ini. > > Can you post your /usr/local/etc/php/extensions.ini? You didn't list > off what extensions you have installed. > cat /usr/local/etc/php/extensions.ini extension=gd.so extension=ctype.so extension=pcre.so extension=session.so extension=bz2.so extension=openssl.so extension=zlib.so extension=mbstring.so extension=mysql.so extension=pdf.so extension=mcrypt.so extension=simplexml.so extension=spl.so extension=mysqli.so extension=xml.so extension=iconv.so extension=hash.so extension=tokenizer.so extension=calendar.so extension=ftp.so extension=xmlrpc.so extension=xmlwriter.so extension=zip.so extension=filter.so ;extension=suhosin.so extension=wddx.so extension=mhash.so extension=json.so extension=dom.so extension=xmlreader.so extension=exif.so extension=ncurses.so extension=gettext.so extension=ldap.so extension=pdo.so extension=soap.so extension=tidy.so extension=pdo_sqlite.so extension=apc.so extension=readline.so extension=xsl.so extension=curl.so ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [Fwd: Suhosin Segmentation Fault]
On Wed, Oct 15, 2008 at 02:47:00PM -0500, Matt wrote: > On Wed, Oct 15, 2008 at 2:35 PM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote: > > On Wed, Oct 15, 2008 at 08:26:09PM +0100, Matthew Seaman wrote: > >> Jeremy Chadwick wrote: > >> > >>> Suhosin is not an extension you load in extensions.ini; it's a patch > >>> applied to the core of PHP. > >> > >> % grep suhosin /usr/local/etc/php/extensions.ini > >> extension=suhosin.so > >> > >> It's both a set of patches to the PHP core, and a loadable module. > >> > >> Cheers, > >> > >> Matthew > > > > Are you sure? > > Yes - the suhosin extension is located in the ports tree at: > /usr/ports/security/php-suhosin > > Install instructions are at: > http://www.hardened-php.net/suhosin/how_to_install_or_upgrade.html#installing_the_extension > > It's been a while since I've looked at the suhosin options and I can't > remember what the differences are between the extension and the > core-php patch. Deep within their forums, I found an answer in a thread. The thread pointed me to this: http://www.hardened-php.net/suhosin/a_feature_list.html "Engine Protection" is not available in security/php-suhosin. Seems to me that the benefits of using the patch version easily outweigh that of the extension version, solely for protection against formatted string vulnerabilities. I also found this amusing tidbit, which is a sticky post on their forum: http://forum.hardened-php.net/viewtopic.php?id=122 That sticky also states that pspell.so will cause Suhosin to crash, advocating that pspell.so must come last in extension.so, but then also advocates simply not using pspell at all. I'm sure that does nothing but confuse users. Seems the OP has also posted there: http://forum.hardened-php.net/viewtopic.php?id=501 It would be interesting to know if the segfaults people experience are specific to the extension version of Suhosin. -- | 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: [Fwd: Suhosin Segmentation Fault]
On Wed, Oct 15, 2008 at 10:01:13PM +0200, Alain Wolf wrote: > On 15.10.2008 20:55, Jeremy Chadwick wrote: > > On Wed, Oct 15, 2008 at 07:25:08PM +0200, Alain Wolf wrote: > >> Not much return on freebsd-isp. > >> I try again here on freebsd-questions. > >> > >> Original-Nachricht > >> Betreff: Suhosin Segmentation Fault > >> Datum: Mon, 13 Oct 2008 09:49:09 +0200 > >> Von: Alain Wolf <[EMAIL PROTECTED]> > >> An: [EMAIL PROTECTED] > >> Newsgruppen: gmane.os.freebsd.isp > >> > >> After upgrading FreeBSD from 6.3-p3 to 6.3-p5 on our server, all > >> websites just display a blank page and every HTTP request created a line > >> as follows in the logs: > >> > >> child pid 80326 exit signal Segmentation fault (11) > >> > >> This same problem happened on another server a few months ago after the > >> upgrade from 6.3-p3 to 6.3-p4, but after a rebuild of all FreeBSD ports > >> all went back to normal. However several rebuilds of all ports did not > >> solve the problem on this one. > >> > >> To narrow down the problem: After disabling the PHP module in Apache the > >> problem disappears. > >> > >> Re-enabling PHP, but disabling the Suhosin extension also works fine. > >> > >> The trick found in this forum, to load the Suhosin extension before all > >> other PHP extensions in /usr/local/etc/php/extensions.ini does not help. > >> In fact not loading any extension at all except Suhosin creates the > >> segfault errors. > > > > Suhosin is not an extension you load in extensions.ini; it's a patch > > applied to the core of PHP. > > Suhosin is *both*. A patch for php and a extension module for PHP. > > >From http://www.hardened-php.net/suhosin/index.html: > Suhosin comes in two independent parts, that can be used separately or > in combination. The first part is a small patch against the PHP core, > that implements a few low-level protections against bufferoverflows or > format string vulnerabilities and the second part is a powerful PHP > extension that implements all the other protections. Except their own website contradicts themselves in many other places, including on their forums *and* in other documentation. I can refer you to some documentation of theirs that states "Suhosin extension sometimes causes other extensions to crash because they try to access internal variables wrongly". You are supposed to use one or the other: the patch, or the extension. You've probably read my other mail by now, so you know that I advocate use of the patch. > The suhosin patch works fine on our servers. But the extension does not. So disable it and use only the patch -- problem solved. I'm CC'ing ale@ on this thread, because he's probably not on -questions, and this has now become a -ports thing. He can comment on what to do about these crashes. I'm of the opinion that security/php-suhosin should be nuked, especially if the patch works fine for everyone but the extension causes problems. > > The extension ordering problem, however, has been thoroughly discussed > > on -ports in the past. It happens to some and not others. There is no > > guaranteed way to determine what works and what doesn't. You have to > > literally enable line-by-line until you figure out which one is causing > > the problem. > > I tried enabling and disabling extensions. All of them work, as long as > suhosin.so is not loaded. Regardless of the order. > > If I disable all other extensions and load only suhosin.so in > /usr/local/etc/php/extensions.ini the apache processes are still crashing. > > > > > You can also try building lang/php5 with DEBUG enabled and then when PHP > > segfaults, run gdb on the coredump and see if you can get a coherent > > backtrace (sometimes difficult with Apache in the way) to see what sort > > of functions are causing the crash; often each extension has its own > > function names, so that might give you some clues. > Hard for me, as this disrupts customer services. We are running without > the extensions for now. > > > > >> PHP (cli) seems to run fine at all times when called from the command-line. > > > > Now that's very interesting, given as the CLI version also loads all the > > extensions listed in extensions.ini. > > > > Can you post your /usr/local/etc/php/extensions.ini? You didn't list > > off what extensions you have installed. > > > > cat /usr/local/etc/php/extensions.ini > extension=gd.so > extension=ctype.so > extension=pcre.
Re: [Fwd: Suhosin Segmentation Fault]
Jeremy Chadwick wrote: You are supposed to use one or the other: the patch, or the extension. Nope, they can be used alone or mixed together (I use both on my servers). For a detailed explanation see: http://www.hardened-php.net/suhosin/why.html I'm CC'ing ale@ on this thread, because he's probably not on -questions, and this has now become a -ports thing. He can comment on what to do about these crashes. Compile PHP in debug and post a backtrace. The suhosin author is a FreeBSD committer, so he can surely help solving the problem. I'm of the opinion that security/php-suhosin should be nuked, especially if the patch works fine for everyone but the extension causes problems. See above. If I disable all other extensions and load only suhosin.so in /usr/local/etc/php/extensions.ini the apache processes are still crashing. Apache version? -- Alex Dupre ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Segmentation fault (core dumped)
tethys ocean wrote:
Hi to all
The server is give this error whenever i want to start apache22. why?
regards
Because something's wrong.
Cheers,
Matthew
What? Not enough of an answer? It's all the answer anyone can give
considering the parcity of information you supply in your question.
To debug this properly could require any or all of:
* your httpd.conf
* the output of
ldd /usr/local/sbin/httpd
* a traceback from httpd.core, although this won't be much use unless
you've compiled httpd with debug symbols.
* the result of running:
truss -f /usr/local/sbin/httpd {+ any other arguments you usually use}
* If you're using mod_php, then the contents of
/usr/local/etc/php/extensions.ini
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
signature.asc
Description: OpenPGP digital signature
Re: Segmentation fault (core dumped)
I have no idea since any other people doing something but i dont know exactly according to their claim he doing some stuff with python for web and i suppose he want to restart apache python perl etc all packet is installed. On Sat, Nov 22, 2008 at 9:36 PM, Kevin Kinsey <[EMAIL PROTECTED]> wrote: > tethys ocean wrote: > >> Hi to all >> >> The server is give this error whenever i want to start apache22. why? >> regards >> > > Well, there could be any number of reasons why this happens. > In my experience, it's because you have Apache loading a > broken or incompatible module. Have you recently rebuilt > Apache, or some other module (like Perl, PHP, Python) that > is used by Apache? > > Kevin Kinsey > -- > If it ain't baroque, don't fix it. >---P.D.Q. Bach > -- Share now a pigeon's flight Bluebound along the ancient skies, Its women forever hair and mammal, A Mediterranean town may arise If you rip apart a pigeon's heart. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Segmentation fault (core dumped)
tethys ocean wrote: Hi to all The server is give this error whenever i want to start apache22. why? regards Well, there could be any number of reasons why this happens. In my experience, it's because you have Apache loading a broken or incompatible module. Have you recently rebuilt Apache, or some other module (like Perl, PHP, Python) that is used by Apache? Kevin Kinsey -- If it ain't baroque, don't fix it. ---P.D.Q. Bach ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Segmentation fault (core dumped)
apache-2.2.9_5 = up-to-date with port
autoconf-2.62 = up-to-date with port
db41-4.1.25_4 = up-to-date with port
gd-2.0.35,1 = up-to-date with port
gdbm-1.8.3_3= up-to-date with port
irc-2.11.2p1= up-to-date with port
ircii-20060725_1= up-to-date with port
nano-2.0.9 = up-to-date with port
p5-HTML-Template-2.9_1 = up-to-date with port
portupgrade-2.4.6,2 = up-to-date with port
py25-MySQLdb-1.2.2 = up-to-date with port
py25-bsddb-2.5.2_2 = up-to-date with port
py25-django-1.0.1 = up-to-date with port
py25-flup-1.0.1 = up-to-date with port
py25-gdbm-2.5.2 = up-to-date with port
python25-2.5.2_3= up-to-date with port
rsync-3.0.4 = up-to-date with port
ruby-1.8.6.287,1= up-to-date with port
ruby18-bdb-0.6.4= up-to-date with port
tcl-8.4.19,1= up-to-date with port
unzip-5.52_5= up-to-date with port
webalizer-2.20.1_2 = up-to-date with port
On Sat, Nov 22, 2008 at 9:39 PM, Matthew Seaman <
[EMAIL PROTECTED]> wrote:
> tethys ocean wrote:
>
>> Hi to all
>>
>> The server is give this error whenever i want to start apache22. why?
>> regards
>>
>>
> Because something's wrong.
>
>Cheers,
>
>Matthew
>
> What? Not enough of an answer? It's all the answer anyone can give
> considering the parcity of information you supply in your question.
> To debug this properly could require any or all of:
>
> * your httpd.conf
> * the output of
> ldd /usr/local/sbin/httpd
/usr/local/sbin/httpd:
libm.so.4 => /lib/libm.so.4 (0x280c7000)
libaprutil-1.so.3 => /usr/local/lib/libaprutil-1.so.3 (0x280dd000)
libdb41.so.1 => /usr/local/lib/libdb41.so.1 (0x280f7000)
libexpat.so.6 => /usr/local/lib/libexpat.so.6 (0x28194000)
libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x281b2000)
libapr-1.so.3 => /usr/local/lib/libapr-1.so.3 (0x2829f000)
libcrypt.so.3 => /lib/libcrypt.so.3 (0x282c1000)
libpthread.so.2 => /lib/libpthread.so.2 (0x282d9000)
libc.so.6 => /lib/libc.so.6 (0x282fe000)
>
>
> * a traceback from httpd.core, although this won't be much use unless
>you've compiled httpd with debug symbols.
locate httpd.core
/usr/local/etc/rc.d/httpd.core
/usr/ports/distfiles/tmp/lib/httpd.core
>
> * the result of running:
>
> truss -f /usr/local/sbin/httpd {+ any other arguments you usually
> use}
truss -f /usr/local/sbin/httpd
truss: cannot open /proc/curproc/mem: No such file or directory
truss: cannot open1 /proc/61323/mem: No such file or directory
>
>
> * If you're using mod_php, then the contents of
> /usr/local/etc/php/extensions.ini
extension=bcmath.so
extension=bz2.so
extension=calendar.so
extension=ctype.so
extension=curl.so
extension=pcre.so
extension=simplexml.so
extension=spl.so
extension=dom.so
extension=filter.so
extension=gd.so
extension=gettext.so
extension=hash.so
extension=iconv.so
extension=json.so
extension=mbstring.so
extension=mcrypt.so
extension=mysql.so
extension=pdo.so
extension=pdo_sqlite.so
extension=posix.so
extension=session.so
extension=sockets.so
extension=sqlite.so
extension=tokenizer.so
extension=xml.so
extension=xmlreader.so
extension=xmlwriter.so
>
>
> --
> Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
> Flat 3
> PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
> Kent, CT11 9PW
>
>
--
Share now a pigeon's flight
Bluebound along the ancient skies,
Its women forever hair and mammal,
A Mediterranean town may arise
If you rip apart a pigeon's heart.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Segmentation fault (core dumped)
On Sat, 22 Nov 2008 21:53:02 +0200, "tethys ocean" <[EMAIL PROTECTED]> wrote: > I have no idea since any other people doing something but i dont know > exactly according to their claim he doing some stuff with python for > web and i suppose he want to restart apache Maybe it's a good idea to avoid messing up with this particular Apache instance then. If you don't know how it has been installed, and you cannot find out, and you are only guessing that a restart should fix things, then don't do that... Geez :P ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Segmentation fault (core dumped)
i found something from bash_hist. he deinstall all pkg. (apache php and python) while he is upgrade. i ve reinstall apache22 and port upgraded. than now i will reinstall all deinstalled package and fix it On Sat, Nov 22, 2008 at 10:12 PM, Giorgos Keramidas < [EMAIL PROTECTED]> wrote: > On Sat, 22 Nov 2008 21:53:02 +0200, "tethys ocean" <[EMAIL PROTECTED]> > wrote: > > I have no idea since any other people doing something but i dont know > > exactly according to their claim he doing some stuff with python for > > web and i suppose he want to restart apache > > Maybe it's a good idea to avoid messing up with this particular Apache > instance then. If you don't know how it has been installed, and you > cannot find out, and you are only guessing that a restart should fix > things, then don't do that... Geez :P > > > -- Share now a pigeon's flight Bluebound along the ancient skies, Its women forever hair and mammal, A Mediterranean town may arise If you rip apart a pigeon's heart. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Segmentation fault (core dumped)
The server is give this error whenever i want to start apache22. why? regards no idea,but most probably you use PHP and added lots of it's modules, some of them crashes ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Segmentation fault (core dumped)
Hi.. I think I know what you are talking about.. What is the output of the command php -v ? any errors? Marwan> Date: Sat, 22 Nov 2008 21:23:24 +0200> From: [EMAIL PROTECTED]> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]> CC: > Subject: Segmentation fault (core dumped)> > Hi to all> > The server is give this error whenever i want to start apache22. why?> regards> > > > -- > Share now a pigeon's flight> Bluebound along the ancient skies,> Its women forever hair and mammal,> A Mediterranean town may arise> If you rip apart a pigeon's heart.> ___> freebsd-questions@freebsd.org mailing list> http://lists.freebsd.org/mailman/listinfo/freebsd-questions> To unsubscribe, send any mail to "[EMAIL PROTECTED]" _ Get more done, have more fun, and stay more connected with Windows Mobile®. http://clk.atdmt.com/MRT/go/119642556/direct/01/___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Segmentation fault (core dumped)
On Sat, 22 Nov 2008 22:52:07 + Marwan Sultan <[EMAIL PROTECTED]> wrote: >I think I know what you are talking about.. >What is the output of the command php -v ? >any errors? I have been have a similar problem lately. ~ $ php -v PHP Warning: PHP Startup: Unable to load dynamic library '/usr/local/lib/php/20060613/sqlite.so' - /usr/local/lib/php/20060613/sqlite.so: Undefined symbol "spl_ce_Countable" in Unknown on line 0 PHP 5.2.6 with Suhosin-Patch 0.9.6.2 (cli) (built: Nov 21 2008 20:45:19) Copyright (c) 1997-2008 The PHP Group Zend Engine v2.2.0, Copyright (c) 1998-2008 Zend Technologies Segmentation fault: 11 (core dumped) I have been trying to correct it without results. -- Jerry [EMAIL PROTECTED] Your lover will never wish to leave you. signature.asc Description: PGP signature
