Re: [PHP4BETA] Test II, PHP 4.0RC2 ahead

From: Date: Sun, 07 May 2000 21:43:15 +0000
Subject: Re: [PHP4BETA] Test II, PHP 4.0RC2 ahead
References: 1  Groups: php.version4 
Request: Send a blank email to php-version4+get-14637@lists.php.net to get a copy of this message
Hi, I am having many problems with RC2. I am using RH6.1/Apache 1.3.9. First, the functions session_start(), session_register(), etc. seem to send some output, as I get the error message "<br> <b>Warning</b>: Cannot send session cookie - headers already sent in <b>session.inc</b> on line <b>736</b><br>" all the time -- where line 736 is the "session_start()" function. If I comment this out, then I get the same error referencing the session_register() function several lines later. Second, I get segfaults about half the time I execute a script, whether from the command line or within apache as a module. The backtrace from the command line execution is: 0x82f11ff in ?? () (gdb) where #0 0x82f11ff in ?? () #1 0x80ba430 in _zval_dtor_wrapper (zvalue=0x85db170) at zend_variables.c:68 #2 0x80bec9a in zend_hash_destroy (ht=0x85dbd54) at zend_hash.c:528 #3 0x80ba569 in _zval_dtor (zvalue=0x85db9e4, __zend_filename=0x81aedbc "zend_execute_API.c", __zend_lineno=237) at zend_variables.c:74 #4 0x80b425f in _zval_ptr_dtor (zval_ptr=0x82322dc, __zend_filename=0x81c98e0 "./zend_execute.c", __zend_lineno=91) at zend_execute_API.c:237 #5 0x8130c4e in execute (op_array=0x8403b1c) at ./zend_execute.c:91 #6 0x8138b98 in execute (op_array=0x85d9a88) at ./zend_execute.c:1614 #7 0x8138b98 in execute (op_array=0x853226c) at ./zend_execute.c:1614 #8 0x813fa90 in execute (op_array=0x8526b08) at ./zend_execute.c:2098 #9 0x8138b98 in execute (op_array=0x8526900) at ./zend_execute.c:1614 #10 0x8138b98 in execute (op_array=0x8358b0c) at ./zend_execute.c:1614 #11 0x813fa90 in execute (op_array=0x8352c7c) at ./zend_execute.c:2098 #12 0x80a2542 in php_execute_script (primary_file=0xbffffcc4) at main.c:1178 #13 0x806d679 in main (argc=3, argv=0xbffffd24) at cgi_main.c:641 I have tried tracking down where this occurs in the script but as soon as I start inserting debug output statements the segfault behavior changes; it's very strange. The following two lines (buried inside a script) NEVER result in a segfault: $this->unserialize(); echo __FILE__ . ":" . __LINE__ . ": \n"; flush(); But if I remove the "echo" line, it ALWAYS segfaults (backtrace above). If I put echo statements inside the "unserialize()" function, sometimes it segfaults, sometimes it doesn't, so I can't get a lock on what statement is causing this. If there is something more helpful I can do, please let me know. BTW, it would be very handy to have a function that will trace execution (i.e., for every line executed output __FILE__ . ":" . __LINE__ . "\n"). Ciao, Andreas Sascha Schumann wrote: > > Hi, > > if you encountered problems with the previous tarball, please > try the new one. We've addressed all possible show stoppers we > know about. > > http://va.php.net/~sas/php-4.0RC2.tar.gz > > Thanks. > > - Sascha > > -- > PHP 4.0 Beta Mailing List <http://www.php.net/version4/> > To unsubscribe, e-mail: php4beta-unsubscribe@lists.php.net > For additional commands, e-mail: php4beta-help@lists.php.net > To contact the list administrators, e-mail: php4beta-admin@lists.php.net

« previous php.version4 (#14637) next »