Bug #10324 Updated: reproducable seg fault during generic script exec with pgsql and mcrypt

ID: 10324 User Update by: kpw@jump9.com Old-Status: Open Status: Closed Bug Type: mcrypt related Operating system: Linux PPC (yellow dog 1.2) PHP Version: 4.0.4pl1 Description: reproducable seg fault during generic script exec with pgsql and mcrypt Previous Comments: --------------------------------------------------------------------------- [2001-07-03 10:48:42] kpw@jump9.com Hi, This still seems to be a problem in 4.0.6. I'm pretty sure that it is caused by specific strings being passed into mycrypt, however, I'm not sure what string characteristics cause the problem. kpw --------------------------------------------------------------------------- [2001-05-27 19:27:02] sniper@php.net Should be fixed in CVS now. Fix will be in PHP 4.0.6. If this happens with it too, reopen this bug report. --Jani --------------------------------------------------------------------------- [2001-04-14 09:54:47] kpw@jump9.com here's the back trace (again without db symbols) of the crash when it happens after my script has completed execution: Program received signal SIGSEGV, Segmentation fault. 0xfe21138 in chunk_free (ar_ptr=0xfebb380, p=0x101f03d8) at malloc.c:3111 3111 malloc.c: No such file or directory. (gdb) bt #0 0xfe21138 in chunk_free (ar_ptr=0xfebb380, p=0x101f03d8) at malloc.c:3111 #1 0xfe20fb0 in __libc_free (mem=0xfebb380) at malloc.c:3023 #2 0xf01121c in ?? () from /etc/apache/libexec/libphp4.so #3 0x0 in ?? () (gdb) --------------------------------------------------------------------------- [2001-04-14 09:46:01] kpw@jump9.com I've rebuilt php with --enable-debug on (rm config.cache & cleaned the build dirs), but the db symbols still don't appear in the back trace. I am using the standard build environment that ships with yellodog/rh 6.2 (gnu), so I am not sure why this isn't working as expected. --------------------------------------------------------------------------- [2001-04-14 07:38:40] derick@php.net Can you try configuring php with --enable-debug, so that better backtraces can be made? --------------------------------------------------------------------------- The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online. Full Bug description available at: http://bugs.php.net/?id=10324