Re: [PHP4BETA] Re: [PHP3] Zend OO syntax overloading support for Java components
| From: | Chad Cunningham | Date: | Wed, 10 Nov 1999 04:27:22 +0000 |
| Subject: | Re: [PHP4BETA] Re: [PHP3] Zend OO syntax overloading support for Java components | ||
| References: | 1 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-6090@lists.php.net to get a copy of this message | ||
Along these lines, I just tried it on my home machine and got core dumps
:( Removing the java support it runs fine. I am using IBM's JDK 1.1.8
and the php CVS as of about 10 PM eastern. Here's a backtrace
Program received signal SIGSEGV, Segmentation fault.
0x4024c3af in object.8 ()
(gdb) bt
#0 0x4024c3af in object.8 ()
#1 0x401dc284 in execute (op_array=0x80e56c0) at zend_execute.c:92
#2 0x401b2bd3 in yy_flex_realloc (ptr=0xbffff810, size=1076201868)
at configuration-scanner.c:1781
#3 0x401f3829 in p_b_symbol (p=0x80e2a04) at regcomp.c:775
#4 0x401f3e24 in allocset (p=0x80e2a04) at regcomp.c:1018
#5 0x401f3e60 in allocset (p=0x80e2a04) at regcomp.c:1021
#6 0x80542f3 in ap_invoke_handler ()
#7 0x80675e9 in process_request_internal ()
#8 0x806764c in ap_process_request ()
#9 0x805f00e in child_main ()
#10 0x805f19c in make_child ()
#11 0x805f2f9 in startup_children ()
#12 0x805f926 in standalone_main ()
#13 0x80600a3 in main ()
#14 0x4007dcb3 in __libc_start_main (main=0x805fd6c <main>, argc=2,
argv=0xbffff9d4, init=0x804e884 <_init>, fini=0x8093d6c <_fini>,
rtld_fini=0x4000a350 <_dl_fini>, stack_end=0xbffff9cc)
at ../sysdeps/generic/libc-start.c:78
rubys@us.ibm.com wrote:
> JVMs are created and destroyed on a per-process basis. For CGI's this
> would be on a per script basis. For Apache, this is configurable, but when
> I test with one client, all I ever get is one JVM which persists until
> Apache is recycled. I'm still looking into other configuration options.
Ah, good :) I have a JavaCC parser I might have use for this, hopefully
that should give me an idea of the load.
> Personally, I feel this is much more natural and usable approach.
Yes, much more intuative.