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 <[email protected]>
> Subject: Re: some help still needed....
> To: Gary Kline <[email protected]>
> Cc: FreeBSD Mailing List <[email protected]>
> X-Mailer: iPad Mail (8J3)
> 
> 
> Always on php the latest.. So php5. 


        And, what's the easiest way to determine why # php segvs?


> 
> On Jun 11, 2011, at 18:11, Gary Kline <[email protected]> wrote:
> 
> > 
> > Guys,
> > 
> > This is both an ACK of thanks to the many listmembers who helped
> > with the last problejm , and a request for further help.  There are
> > at least a couple thing that plague me when I try to get back to
> > where things were before I _finally_ tracked the named/bin problem
> > to it being a bad switch.
> > 
> > The first is that php now keeps coring on me.  It's a segv.
> > According to the FBSD  forums, if I comment-out all the
> > php5-extensions, I will eventually figure out what's causing php to
> > segv.  Is this the only way? or the easiest way?  
> > 
> > Should I be using php5 or php52, or no-diff?  I'm using php5.5.3.6
> > 
> > 
> > 
> > tia,
> > 
> > gary
> > 
> > 
> > -- 
> > Gary Kline  [email protected]  http://www.thought.org  Public Service Unix
> >           Journey Toward the Dawn, E-Book: http://www.thought.org
> >          The 8.51a release of Jottings: http://jottings.thought.org
> > 
> > _______________________________________________
> > [email protected] mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to "[email protected]"
> 

-- 
 Gary Kline  [email protected]  http://www.thought.org  Public Service Unix
           Journey Toward the Dawn, E-Book: http://www.thought.org
          The 8.51a release of Jottings: http://jottings.thought.org

_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[email protected]"

Reply via email to