Date: Wed, 15 Jun 2011 10:49:26 +0200 From: Damien Fleuriot <ml@my.gd> To: freebsd-questions@freebsd.org, kline@thought.org Subject: Re: some help still needed.... Message-ID: <4DF87216.5050908@my.gd> In-Reply-To: <20110611233610.GA11510@thought.org> References: <20110611231109.GA10815@thought.org> <E8E6A9AF-2CB6-457B-B1D4-5C6878047990@d3photography.com> <20110611233610.GA11510@thought.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/12/11 1:36 AM, Gary Kline wrote: > On Sat, Jun 11, 2011 at 06:22:57PM -0500, Ryan Coleman wrote: >> Date: Sat, 11 Jun 2011 18:22:57 -0500 >> From: Ryan Coleman <editor@d3photography.com> >> Subject: Re: some help still needed.... >> To: Gary Kline <kline@thought.org> >> Cc: FreeBSD Mailing List <freebsd-questions@FreeBSD.ORG> >> X-Mailer: iPad Mail (8J3) >> >> >> Always on php the latest.. So php5. > > > And, what's the easiest way to determine why # php segvs? > Sorry for the late response Gary. First, I would ask myself: - does it crash in CLI ? - does it crash as an apache module ? - does it crash as a PHP FCGI process ? Second, I would ask myself: - does it crash when I call a specific php page ? - any page at all ? Third, I would rebuild php with debug: cd /usr/ports/lang/php5 && make config Tick DEBUG. Of course you'll also want to rebuild your php5-extensions just to be safe. When you next get a core dump, you should be able to load it in gdb and see what module caused it to crash.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DF87216.5050908>