# "Segmentation fault" w/ php5.0.0rc3 on macosx10.3.4

- Thread: https://externals.io/message/10544
- Original archive: https://news-web.php.net/php.internals/10544
- Started by OpenMacNews on 2004-06-16T20:18:52+00:00
- Messages: 4
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #10544 — OpenMacNews — 2004-06-16T20:18:52+00:00

URL: https://externals.io/message/10544#10544

hi all,

i'd posted this on the phpgacl list, and a kind soul there suggested to try here ...

i'm looking for any/help help in starting to debug this.

thx,

richard

> > […]

> hi,
>
> i'm trying to setup phpgacl-3.3.1 with *existing* instances of Smarty (cvs head) & ADODB422 on
> 	MacOSX 10.3.4.
> 	Apache/2.1.0-dev (cvs head)
> 	Perl v5.8.4
> 	postgreSQL v7.4.2
> 	php 5.0.0RC3 + Turck-mmcache (cvs head)
>
> everything works great pre-phpgacl ...
>
> i've made changes to phpgacl files, per "Advanced Setup", to ADODB_DIR, smarty_dir, etc.
>
> upon pgpgacl setup <http://testdomain.internal.com/admin/phpgacl/setup.php>, i get:
>
> 	Configuration:
> 	 driver = postgres7,
> 	 host = testdomain.internal.com,
> 	 user = authuser,
> 	 database = auth_db,
> 	 table prefix = gacl_
>
> 	Testing database connection...
> 	Success! Connected to "postgres7" database on "testdomain.internal.com".
>
>
> 	Testing database type...
> 	Success! Compatible database type "postgres7" detected!
> 	 Making sure database "auth_db" exists...
> 	Success! Good, database "auth_db" already exists!
> 	Success! Installation Successful!!!
>
> 	 *IMPORTANT*
> 	Please make sure you create the <phpGACL root>/admin/templates_c directory, and give it write permissions for the user your web server runs as.
>
> 	Please read the manual, and example.php to familiarize yourself with phpGACL.
>
> 	Let's get started!
>
> after ensuring write permission are all ok, when i subsequently click on the "Let's get started" link --> <http://testdomain.internal.com/admin/phpgacl/admin/about.php?first_run=1>
>
> I get a browser error of:
>
> 	Safari can't open the page
> 	"http://testdomain.internal.com/admin/phpgacl/admin/about.php" because it could not load data from this location.
>
> checking apache's error log, i find that one of my server thread dies with:
>
> 	[Wed Jun 16 11:55:26 2004] [notice] child pid 2663 exit signal Segmentation fault (11)
>
> not really informative for me ... any suggestion/help as to where to BEGIN to start debugging this? yes, i know, i've a lot of "variables" in my sety :S
>
> thanks,
>
> richard
>
> fwiw,  apache/server-info shows:
>
> 	Server Version: Apache/2.1.0-dev (Unix) mod_perl/1.99_15-dev Perl/v5.8.4 DAV/2 PHP/5.0.0RC3 mod_auth_pgsql/2.0.2b1
> 	Server Built: Jun 9 2004 18:37:10
> 	API Version: 20040425:1
> 	Hostname/port: testdomain.internal.com:80
> 	Timeouts: connection: 300    keep-alive: 300
> 	MPM Name: Worker
> 	MPM Information: Max Daemons: 1 Threaded: yes Forked: yes
> 	
> and php -i shows:
>
> PHP Version => 5.0.0RC3
>
> 	System => Darwin testdomain.internal.com 7.4.0 Darwin Kernel Version 7.4.0: Wed May 12 16:58:24 PDT 2004; root:xnu/xnu-517.7.7.obj~7/RELEASE_PPC  Power Macintosh
> 	Build Date => Jun 10 2004 00:44:23
> 	Configure Command =>  './configure' '--disable-debug' '--prefix=/usr' '--with-layout=PHP' '--with-config-file-path=/etc/php5' '--sysconfdir=/etc/php5' '--enable-shared' '--disable-static' '--libdir=/System/Library/PHP' '--includedir=/usr/include' '--mandir=/usr/local/man' '--localstatedir=/var/php4' '--with-db4=/usr' '--with-pgsql=/usr/local/pgsql' '--without-mysql' '--enable-cli' '--with-pear=/System/Library/PHP' '--disable-cgi' '--with-apxs2=/usr/sbin/apxs' '--disable-dmalloc'
> '--with-tsrm-pthreads' '--enable-shmop' '--enable-sockets' '--enable-inline-optimization' '--enable-xml' '--enable-libxml' '--with-libxml-dir=/usr' '--with-java=/Library/Java/Home' '--with-openssl=/usr/local/ssl' '--with-openssl-dir=/usr/local/ssl' '--with-zlib' '--with-zlib-dir=/usr' '--with-imap=/usr/local/imap' '--enable-mailparse' '--with-imap-ssl=/usr/local/ssl' '--with-mcrypt' '--with-mhash' '--with-gmp=/usr/local' '--with-curl=/usr' '--with-gd=/usr/local/gd' '--with-png-dir=/usr/local'
> '--with-jpeg-dir=/usr/local' '--with-tiff-dir=/usr/local' '--enable-magic-quotes' '--enable-calendar' '--with-kerberos=/usr' '--with-freetype-dir=/usr/X11R6' '--with-xpm-dir=/usr/X11R6' '--enable-exif' '--enable-mbstring' '--enable-ftp' '--enable-bcmath'
> 	Server API => Command Line Interface
> 	Virtual Directory Support => enabled
> 	Configuration File (php.ini) Path => /etc/php5/php.ini
> 	PHP API => 20031224
> 	PHP Extension => 20040412
> 	Zend Extension => 220040412
> 	Debug Build => no
> 	Thread Safety => enabled
> 	IPv6 Support => enabled
> 	Registered PHP Streams => php, file, http, ftp, compress.zlib, https, ftps
> 	Registered Stream Socket Transports => tcp, udp, unix, udg, ssl, tls
> 	This program makes use of the Zend Scripting Language Engine:
> 	Zend Engine v2.0.0RC3, Copyright (c) 1998-2004 Zend Technologies
> 		with Turck MMCache v2.4.7-CVS, Copyright (c) 2002-2003 TurckSoft, St. Petersburg, by Dmitry Stogov

---

## #10545 — Dan Kalowsky — 2004-06-16T21:49:22+00:00

URL: https://externals.io/message/10544#10545 · In reply to: #10544

A good start would be to move away from a completely developer environment 
like you're using.  I'd suggest either working with PHP5 or Apache2-dev, 
but not both at the same time.  That should help you narrow things down a 
bit more.  In reality, I'd narrow to Apache1 as well if you're trying to 
debug some bit of code in PHP.



> hi all,
>
> i'd posted this on the phpgacl list, and a kind soul there suggested to try 
> here ...
>
> i'm looking for any/help help in starting to debug this.
>
> thx,
>
> richard
>
> > […]
>
> > […]
>
>

>---------------------------------------------------------------<
Dan Kalowsky			"I thought you died alone,
http://www.deadmime.org/~dank	 a long long time ago."
dank-nom@aps-deadmime.org	 - "The Man Who Sold the World"
kalowsky@php.net		 	David Bowie

---

## #10546 — OpenMacNews — 2004-06-16T21:56:14+00:00

URL: https://externals.io/message/10544#10546 · In reply to: #10545

-- On Wednesday, June 16, 2004 2:49 PM -0700  Dan Kalowsky <dank@deadmime.org> wrote:

> A good start would be to move away from a completely developer environment like you're using.  I'd suggest either working with PHP5 or Apache2-dev, but not both at the same time.  That should help you narrow things down a bit more.  In reality, I'd narrow to Apache1 as well if you're trying to debug some bit of code in PHP.

fair point, but its exactly this "manybody" developer environment i'm trying to debug.  i've had do other probs (so far ...) w/ the setup i'm using.

if seems that something in the phpgacl 'stuff' is causing php5+apache to choke ... the question -- for me -- is HOW to track down WHAT the issue is.

that said, THIS problem is reproducible with apache 2.0.49 as well ...

richard

---

## #10548 — Dan Kalowsky — 2004-06-16T22:04:09+00:00

URL: https://externals.io/message/10544#10548 · In reply to: #10546

Well if you wish to continue adding more challenges to solving your 
goal, you could add in the latest CVS versions of gcc as well.

Honest, your best bet to start debugging this is to place PHP5+PGPGACL 
into a stable environment.  If it doesn't reproduce there, introduce a 
semi-stable environment (i.e. any recent Apache2 release).  Again if it 
doesn't reproduce there, move to your extremely volitile setup you've 
got currently and hope for a chance to attach your debugger to it.

Personally, I'd start with the PHP5 cgi/cli and see if it happens 
there.  Easiest way to reproduce and debug the code.



> -- On Wednesday, June 16, 2004 2:49 PM -0700  Dan Kalowsky 
> <dank@deadmime.org> wrote:
>
> > […]
>
> fair point, but its exactly this "manybody" developer environment i'm 
> trying to debug.  i've had do other probs (so far ...) w/ the setup 
> i'm using.
>
> if seems that something in the phpgacl 'stuff' is causing php5+apache 
> to choke ... the question -- for me -- is HOW to track down WHAT the 
> issue is.
>
> that said, THIS problem is reproducible with apache 2.0.49 as well ...
>
> richard
