#22638 [NoF->Opn]: Using Horde/IMP to read an email causes a crash

From: Date: Fri, 28 Mar 2003 09:59:38 +0000
Subject: #22638 [NoF->Opn]: Using Horde/IMP to read an email causes a crash
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-36645@lists.php.net to get a copy of this message
ID: 22638 Updated by: edink@php.net Reported By: dsilvers at pepperfish dot net -Status: No Feedback +Status: Open Bug Type: IMAP related Operating System: Linux PHP Version: 4.3.2RC Previous Comments: ------------------------------------------------------------------------ [2003-03-28 03:36:23] spamfree at orangechicken dot com Please don't close this bug. It happens in 4.3.1 as well. Here's the minimum code that causes a crash: $inbox = imap_open( '{' . MAIL_SERVER . '/pop3:110}INBOX', MAIL_USER, MAIL_PASS ); Here's the compile string: './configure' '--with-apxs=/usr/local/apache/bin/apxs' '--with-xml' '--enable-bcmath' '--enable-calendar' '--with-curl' '--enable-ftp' '--with-gd' '--with-jpeg-dir=/usr/local' '--with-png-dir=/usr' '--with-xpm-dir=/usr/X11R6' '--with-imap' '--with-imap-ssl' '--with-kerberos' '--with-mcrypt' '--enable-magic-quotes' '--with-mysql' '--with-pear' '--enable-xslt' '--with-xslt-sablot' '--enable-sockets' '--enable-track-vars' '--with-ttf' '--with-freetype-dir=/usr' '--enable-gd-native-ttf' '--enable-versioning' '--with-zlib' What else do I need? It seems like the code is quite minimum to cause the crash (1 line). ------------------------------------------------------------------------ [2003-03-24 04:17:30] sniper@php.net No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you. ------------------------------------------------------------------------ [2003-03-18 20:12:35] sniper@php.net Reclassified, assuming the problem is caused by the imap functions. What c-client version are you using?? (it's most likely that what is causing the crash, and not PHP code) What part of IMP causes the crash? Reading it from the imap server? Processing the mail? Please try and add some debug die() lines or something to figure out what exactly causes the crash. ------------------------------------------------------------------------ [2003-03-18 13:35:41] dsilvers at pepperfish dot net Right. With the snapshot: php4-STABLE-200303181830 I get exactly the same outward behaviour (I.E. PHP dies when I read a message with a 'CC: <>' header in it. This is the gdb: Program received signal SIGSEGV, Segmentation fault. 0x402d29d1 in malloc () from /lib/libc.so.6 (gdb) bt #0 0x402d29d1 in malloc () from /lib/libc.so.6 #1 0x402d2074 in malloc () from /lib/libc.so.6 #2 0x0811debc in _emalloc (size=12) at /home/dsilvers/new-webmail/php4-STABLE-200303181830/Zend/zend_alloc.c:158 #3 0x0813a1dd in execute (op_array=0x8334174) at /home/dsilvers/new-webmail/php4-STABLE-200303181830/Zend/zend_execute.c:1601 #4 0x0813a3b4 in execute (op_array=0x8406dcc) at /home/dsilvers/new-webmail/php4-STABLE-200303181830/Zend/zend_execute.c:1650 #5 0x0812af28 in zend_execute_scripts (type=8, retval=0x0, file_count=3) at /home/dsilvers/new-webmail/php4-STABLE-200303181830/Zend/zend.c:864 #6 0x08108caa in php_execute_script (primary_file=0xbffffe48) at /home/dsilvers/new-webmail/php4-STABLE-200303181830/main/main.c:1647 #7 0x081454b3 in main (argc=1, argv=0xbffffec4) at /home/dsilvers/new-webmail/php4-STABLE-200303181830/sapi/cgi/cgi_main.c:1480 Any ideas? ------------------------------------------------------------------------ [2003-03-11 20:44:08] sniper@php.net Please try using this CVS snapshot: http://snaps.php.net/php4-STABLE-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-STABLE-latest.zip And what part of IMP causes the crash? Reading it from the imap server? Processing the mail? ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/22638 -- Edit this bug report at http://bugs.php.net/?id=22638&edit=1

« previous php.bugs (#36645) next »