Date: Wed, 15 Jun 2011 19:18:58 -0500 From: "Jack L. Stone" <jacks@sage-american.com> To: Ryan Coleman <editor@d3photography.com> Cc: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Another PHP5 problem Message-ID: <3.0.1.32.20110615191858.018e54e0@sage-american.com> In-Reply-To: <233F0997-C03D-4C0D-9435-2975B932C31E@d3photography.com> References: <3.0.1.32.20110615175738.019581f8@sage-american.com> <3.0.1.32.20110615155910.019581f8@sage-american.com> <3.0.1.32.20110615150619.019581f8@sage-american.com> <3.0.1.32.20110615090401.0181fea8@sage-american.com> <3.0.1.32.20110615090401.0181fea8@sage-american.com> <3.0.1.32.20110615150619.019581f8@sage-american.com> <3.0.1.32.20110615155910.019581f8@sage-american.com> <3.0.1.32.20110615175738.019581f8@sage-american.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 06:35 PM 6/15/2011 -0500, Ryan Coleman wrote: >That wouldn't likely cause a segfault, but you could use your apache logs to see if there's something in the last file before the segfault occurs... but that could be a wild goose chase. > > >On Jun 15, 2011, at 5:57 PM, Jack L. Stone wrote: > >> At 04:04 PM 6/15/2011 -0500, Ryan Coleman wrote: >>> My solution for these issues is usually pretty easy: >>> Disable all extensions (with a ; before the line) and then re-enable >> batches until it dies on you and then go through line-by-line to see which >> one did it. >>> >>> Should take about 5 minutes, tops, to run through the entire list. >>> Ryan: Found it! 2 extensions were the problem: # extension=sqlite3.so # extension=pdo_sqlite.so Don't even know why they got in there.... (except I checked the boxes in make config) Thanks for the great idea! Jack (^_^) Happy trails, Jack L. Stone System Admin Sage-american
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.1.32.20110615191858.018e54e0>