PHP 4.0 Bug #3228 Updated: Odd behaviour (sybase related?)
| From: | Bug Database | Date: | Mon, 17 Jan 2000 05:33:41 +0000 |
| Subject: | PHP 4.0 Bug #3228 Updated: Odd behaviour (sybase related?) | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-14696@lists.php.net to get a copy of this message | ||
ID: 3228
User Update by: simon@airdmhor.gen.nz
Status: Open
Bug Type: Misbehaving function
Description: Odd behaviour (sybase related?)
Another crash happened. Hmm, maybe it's a broken build system? I think the sysadmin upgraded
some stuff a couple of weeks ago. How would I tell?
[Mon Jan 17 18:31:50 2000] Script: '/home/simonr/www/htdocs/class.crash.php'
---------------------------------------
zend_execute_API.c(216) : Block 0x081DAEB8 status:
zend_variables.c(63) : Actual location (location was relayed)
Beginning: Overrun (magic=0x2A8FCC84, expected=0x7312F8DC)
End: Unknown
---------------------------------------
[Mon Jan 17 18:31:51 2000] [notice] child pid 12754 exit signal Segmentation fault (11), possible
coredump in /home/simonr/www
(gdb) bt
#0 0x8082615 in destroy_zend_class ()
#1 0x808a2e3 in zend_hash_clean ()
#2 0x808a451 in zend_hash_apply ()
#3 0x807cbbb in shutdown_compiler ()
#4 0x8086af3 in zend_deactivate ()
#5 0x8076762 in php_request_shutdown ()
#6 0x80e7a79 in ap_run_cleanup ()
#7 0x80e6123 in ap_clear_pool ()
#8 0x80e61a3 in ap_destroy_pool ()
#9 0x80f6353 in ap_child_terminate ()
#10 0x80f6578 in ap_child_terminate ()
#11 0x80f6908 in ap_child_terminate ()
#12 0x80f6e7c in ap_child_terminate ()
#13 0x80f74ac in main ()
#14 0x401dfcb3 in __libc_start_main (main=0x80f7124 <main>, argc=1, argv=0xbffffa44,
init=0x805ea0c <_init>,
fini=0x812bd8c <_fini>, rtld_fini=0x4000a350 <_dl_fini>, stack_end=0xbffffa3c) at
../sysdeps/generic/libc-start.c:78
(gdb)
Full Bug description available at: http://bugs.php.net/version4/?id=3228