PHP 4.0 Bug #7169 Updated: Crash with long .php-file and --trans-sid

From: Date: Fri, 13 Oct 2000 09:50:09 +0000
Subject: PHP 4.0 Bug #7169 Updated: Crash with long .php-file and --trans-sid
Groups: php.dev 
Request: Send a blank email to php-dev+get-34880@lists.php.net to get a copy of this message
ID: 7169 User Update by: balu@technologist.com Status: Open Bug Type: Reproduceable crash Description: Crash with long .php-file and --trans-sid I configured it on the original system with: ./configure --with-apxs=/usr/local/apache/current/bin/apxs --enable-versioning --with-mysql --enable-track-vars --enable-syvshm --enable-sysvsem --with-config-file-path=/etc --enable-url-includes --enable-trans-sid On a second system I used: ./configure --prefix=/usr --libexecdir=/usr/libexec/php --sysconfdir=/etc/ --sharedstatedir=/var/state/php --localstatedir=/var/state/php --with-apxs --enable-versioning --enable-inline-optimization --enable-calendar --with-gdbm --enable-ftp --with-gettext --with-mysql=/usr --enable-trans-sid --enable-sysvsem --enable-sysvshm --with-zlib --with-config-file-path=/etc/php.ini I can't get a logfile, so I used: gdb /usr/local/apache/current/bin/httpd (gdb) run -X and got (before accessing the page) Starting program: /usr/local/apache/current/bin/httpd -X warning: find_solib: Can't read pathname for load map: Input/output error Error while mapping shared library sections: "/sbin/": not in executable format: Is a directory. Error while reading shared library symbols: "/sbin/": can't read symbols: Is a directory. Cannot access memory at address 0xc3815b00. (gdb) But I think that is a gdb-problem... Previous Comments: --------------------------------------------------------------------------- [2000-10-12 18:24:49] balu@technologist.com I have problems accessing a rather long file after enabling --trans-sid. Apache-childs die after processing X lines of that file. (I tested to add one more char at the end of the last processed character, but it was not displayed) Is it possible that the buffer --trans-sid uses to store the page (and process it) in is too small? I have no gdb installed yet, or can create a logfile, so perhaps this could be approved by someone else... I will try to reproduce it on another system and get a trace from that... --------------------------------------------------------------------------- Full Bug description available at: http://bugs.php.net/?id=7169

« previous php.dev (#34880) next »