Date: Thu, 09 Oct 2008 13:15:59 +0200 From: Laszlo Nagy <gandalf@shopzeus.com> To: Jeremy Chadwick <koitsu@FreeBSD.org>, freebsd-questions@freebsd.org Subject: Re: php5 segfault Message-ID: <48EDE7EF.1090601@shopzeus.com> In-Reply-To: <20081009100047.GA523@icarus.home.lan> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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 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. Thank you! Laszlo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48EDE7EF.1090601>