#48258 [Opn->Fbk]: imap_header crash without any response when to: or cc: is very long

ID: 48258 Updated by: pajoye@php.net Reported By: rimgaudas dot laucius at delfi dot lt -Status: Open +Status: Feedback Bug Type: IMAP related Operating System: linux-windows PHP Version: 5.2.9 New Comment: Please install the debug symbols or compile PHP in debug mode. Which c-client do you use? If it is an old version (<2007) please try using 2007e. Previous Comments: ------------------------------------------------------------------------ [2009-05-13 08:01:40] rimgaudas dot laucius at delfi dot lt Description: ------------ failure noticed when "to:" was 14 KB long and another failure noticed when "cc:" was 34 KB long. here stacktrace (with php 5.2.8, but 5.2.9 crash as well): This GDB was configured as "i686-pld-linux"...(no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (gdb) run imaptest.php Starting program: /usr/bin/php imaptest.php (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1215653088 (LWP 26789)] [New Thread -1232208976 (LWP 26792)] [Thread -1232208976 (zombie) exited] test Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1215653088 (LWP 26789)] 0xb7938afc in memcpy () from /lib/tls/libc.so.6 (gdb) bt #0 0xb7938afc in memcpy () from /lib/tls/libc.so.6 #1 0xb6ed420f in rfc822_skip_comment () from /usr/lib/libc-client.so.2006k #2 0xb6ed4255 in rfc822_skip_comment () from /usr/lib/libc-client.so.2006k #3 0xb6ed4c0b in rfc822_output_address () from /usr/lib/libc-client.so.2006k #4 0xb6ed497d in rfc822_output_address_list () from /usr/lib/libc-client.so.2006k #5 0xb6fac3c2 in zif_imap_mime_header_decode () from /usr/lib/php/imap.so #6 0x00000029 in ?? () #7 0x00000000 in ?? () (gdb) Quit ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=48258&edit=1