Bug #18104 Updated: imap_open() results in apache child pid exit segfaul sig (11)

ID: 18104 Updated by: sniper@php.net Reported By: lnxgeek@us.ibm.com -Status: Open +Status: Feedback Bug Type: IMAP related Operating System: Red Hat Linux 7.3 PHP Version: 4.2.1 New Comment: Keep this at 'feedback' until you can get us that GDB backtrace.. Previous Comments: ------------------------------------------------------------------------ [2002-07-02 23:54:17] lnxgeek@us.ibm.com Yup, I understand you don't want the core file. I know that _I_ want the core file so I can give you a bt. I'll try again. And yes, I already tried _both_ sets of directions. Neither one did me good. That said, I've narrowed the problem down to issues with php 4.2.1 / 4.1.2 imap module. The segfault will ONLY happen when trying to use CRAM-MD5 mech for authentication. If the imapd does not advertise CRAM-MD5 then PLAIN is used and everything works as expected. That said, I check out the mtest tool provided with imap-2001a and verified that mtest will correctly login to an imap server with CRAM-MD5. PHP however continues to segfault when trying to do the same login with CRAM-MD5. I'm fairly certain this narrows the issue down to somethig having to do with MD5 auth in php4/ext/imap/imap.c and NOT the imap-2001a c-client libs. For a simple test case I recomend the script posted in this bug report and to verify it works against an imapd server that advertises MD5-CRAM. I'm using Cyrus IMAPd 2.1.5 with SASL 2.1.5 for my tests. ------------------------------------------------------------------------ [2002-07-02 13:16:39] sniper@php.net Open this page: http://bugs.php.net/bugs-generating-backtrace.php And look under the topic 'If you can't get a core file' for the instructions how to get a backtrace. We _do_not_ want any core file, we want the GDB backtrace.. ------------------------------------------------------------------------ [2002-07-02 11:40:08] lnxgeek@us.ibm.com Sniper - Thanks much for the suggestions. I've followed the directions as indecated in my updates of last night but am not able to get a core file. Is it expected that with --enable-debug that errors no longer appear in /var/log/http/error_log ? Do you have any suggestions in addition to what is at that URL for getting a core dump? I agree, a core dump is needed to figure out more. It's just a matter of getting one and I'm looking for a bit of help on that from someone who has done core dumps with php/apache before. Thanks much. ------------------------------------------------------------------------ [2002-07-02 08:42:33] sniper@php.net Thank you for this bug report. To properly diagnose the problem, we need a backtrace to see what is happening behind the scenes. To find out how to generate a backtrace, please read http://bugs.php.net/bugs-generating-backtrace.php Once you have generated a backtrace, please submit it to this bug report and change the status back to "Open". Thank you for helping us make PHP better. There you can find out how to get backtrace without a core file.. ------------------------------------------------------------------------ [2002-07-02 04:12:15] lnxgeek@us.ibm.com Another fun thing I did to see if this would work is I checked out the current php4/ext/imap/* files from CVS tonight and added them to the php 4.2.1 src replacing the files that were there. Built again with --enable-debug and attempted all the tests documented above. Received the same results. *sigh* Now it's time for sleep. Still cannot get a backtrace. Any hints on doing so would be great. ------------------------------------------------------------------------ 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/18104 -- Edit this bug report at http://bugs.php.net/?id=18104&edit=1