Date: Thu, 9 Oct 2008 05:05:40 -0700 From: Jeremy Chadwick <koitsu@FreeBSD.org> To: Laszlo Nagy <gandalf@shopzeus.com> Cc: freebsd-questions@freebsd.org Subject: Re: php5 segfault Message-ID: <20081009120540.GA3677@icarus.home.lan> In-Reply-To: <48EDE7EF.1090601@shopzeus.com> References: <48ECACB4.8080103@shopzeus.com> <20081008131248.GA77388@icarus.home.lan> <gcirs1$iak$1@ger.gmane.org> <EA000AF4-02F5-4515-9257-48736A51B4B8@quinn.com> <48EDBCB1.7020803@shopzeus.com> <20081009081741.GA98538@icarus.home.lan> <48EDD487.7090401@shopzeus.com> <20081009100047.GA523@icarus.home.lan> <48EDE7EF.1090601@shopzeus.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 09, 2008 at 01:15:59PM +0200, Laszlo Nagy wrote: > >> I thought you said you changed the order and it didn't work? *confused* >> > I said no success so far. There are more than 20 modules and there is no > description about what the good order should be. I had to keep trying... >> If so: it should be obvious why it hasn't been fixed. It doesn't appear >> to affect everyone -- for example, we have never seen this problem in >> the 4-5 years we've been using PHP on FreeBSD -- and the solution >> doesn't really make much sense anyway. It smells of a missing symbol >> problem (e.g. libxx.so wants a symbol named "hello_bob", but the symbol >> is available in libyy.so, which has to be loaded first; however, ld.so >> and dlopen(3) have explicit handling for this scenario (see RTLD_NOW vs. >> RTLD_LAZY), so I'm at a loss). >> > Maybe you are right. But I would think that a missing symbol problem > should throw an error message telling "missing symbol" instead of making > a segfault. That all depends on the C code. If you'd like to dig around in it and investigate/debug it to find out what the true nature of the problem is, that would be beneficial, since AFAIK no one has done that yet. It's all speculative. >> That said, if you feel this is a humongous issue, I highly recommend you >> mail the PHP port maintainer and express your concerns, or open a PR >> > We had the same problem on our previous server. I'm going to install > another box today and test it. If the problem comes out again, I'm going > to write a PR. And I would also recommend filing a bug report with the PHP folks. This may be something that's a PHP problem and not a FreeBSD problem. It may "not be a Linux problem" because for all we know the Linux RPMs and Portage stuff in CentOS/Gentoo could have workarounds in place. -- | Jeremy Chadwick jdc 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 |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081009120540.GA3677>