Looks like the one. Thanks
Alan Knowles wrote:
Is this the sqlite "build it with gawk" bug?
Regards
Alan
On Wed, 2005-03-30 at 11:09 +1000, Nick Loeve wrote:
Sorry here is the BT from GDB
(gdb) run
Starting program: /home/nick/Desktop/build-src/php-src/sapi/cli/php
[Thread debugging using libthread
Is this the sqlite "build it with gawk" bug?
Regards
Alan
On Wed, 2005-03-30 at 11:09 +1000, Nick Loeve wrote:
> Sorry here is the BT from GDB
>
> (gdb) run
> Starting program: /home/nick/Desktop/build-src/php-src/sapi/cli/php
> [Thread debugging using libthread_db enabled]
> [New Thread 1076758
Sorry here is the BT from GDB
(gdb) run
Starting program: /home/nick/Desktop/build-src/php-src/sapi/cli/php
[Thread debugging using libthread_db enabled]
[New Thread 1076758816 (LWP 13474)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1076758816 (LWP 13474)]
zend_hash_m
I was just wondering if i should report this as a bug?
I have the latest CVS 5.1 code, and i can build it ok, but when PHP
segfaults on startup.
I am using Ubuntu Hoary on a P4.
./configure --prefix=/usr/local/php5
--with-config-file-path=/usr/local/php5/lib
make
The SAPI's build ok, but if i r