Edit report at http://bugs.php.net/bug.php?id=53292&edit=1

 ID:                 53292
 Comment by:         chrisst at carmel dot ac dot uk
 Reported by:        mmitchell at riccagroup dot com
 Summary:            imap_header crashes when too may To: addresses exist
 Status:             Open
 Type:               Bug
 Package:            IMAP related
 Operating System:   Windows
 PHP Version:        5.2.14
 Block user comment: N
 Private report:     N

 New Comment:

Agreed with mmitchell, I am also experiencing this issue.  Would be
great if this could be ported to 5.2.x.


Previous Comments:
------------------------------------------------------------------------
[2010-11-11 18:51:13] mmitchell at riccagroup dot com

Works with 5.3.3 VC6 Thread Safe!

Works with 5.3.3 VC9 Thread Safe!



Still fails with 5.2.14 even with minimal config where php_imap is the
only ext loaded.



I guess whatever change in 5.3 fixed this should be back ported to 5.2?

------------------------------------------------------------------------
[2010-11-11 18:32:47] paj...@php.net

I mean the bug not to get a backtrace.

------------------------------------------------------------------------
[2010-11-11 18:30:43] paj...@php.net

Try with 5.3.3 please.

------------------------------------------------------------------------
[2010-11-11 18:06:57] mmitchell at riccagroup dot com

I tried to do a better back trace this time. I was missing the entry in
the debug symbol path this time that downloads the microsoft debug
symbols.



My Symbol search path is 

"C:\php;C:\php\ext;SRV*c:\symbols*http://msdl.microsoft.com/download/symbols";



For some reason I still get 



"WARNING - DebugDiag was not able to locate debug symbols for
C:\php\ext\php_imap.dll, so the information below may be incomplete."



But the .pdb file is at C:\php\ext\php_imap.pdb so I'm not sure why it
can't find it. Any ideas?

------------------------------------------------------------------------
[2010-11-11 16:47:31] mmitchell at riccagroup dot com

I did a backtrace but it seems to crash in ntdll.dll and I don't know if
any of this is useful. I'm not sure how to upload the backtrace file so
I will just paste the parts that seem to be important here. 





Thread 0 - System ID 11372

Entry point   php+2f72 

Create time   11/11/2010 1:15:22 AM 

Time spent in user mode   0 Days 0:0:3.843 

Time spent in kernel mode   0 Days 0:0:0.312 



Function     Arg 1     Arg 2     Arg 3   Source 

ntdll!RtlSubtreePredecessor+195     00411028     00411044     00411028  


super long list here.....



NTDLL!RTLSUBTREEPREDECESSOR+195WARNING - DebugDiag was not able to
locate debug symbols for ntdll.dll, so the information below may be
incomplete.









In
php__PID__3540__Date__11_11_2010__Time_01_15_39AM__469__Second_Chance_Exception_C0000005.dmp
the assembly instruction at ntdll!RtlSubtreePredecessor+195 in
C:\WINDOWS\system32\ntdll.dll from Microsoft Corporation has caused an
access violation exception (0xC0000005) when trying to write to memory
location 0x00410fb0 on thread 0



Module Information 

Image Name: C:\WINDOWS\system32\ntdll.dll   Symbol Type:  Export 

Base address: 0x7c800000   Time Stamp:  Mon Feb 09 06:02:56 2009  

Checksum: 0x000c2b9d   Comments:   

COM DLL: False   Company Name:  Microsoft Corporation 

ISAPIExtension: False   File Description:  NT Layer DLL 

ISAPIFilter: False   File Version:  5.2.3790.4455
(srv03_sp2_gdr.090203-1205) 

Managed DLL: False   Internal Name:  ntdll.dll 

VB DLL: False   Legal Copyright:  © Microsoft Corporation. All rights
reserved. 

Loaded Image Name:  ntdll.dll   Legal Trademarks:   

Mapped Image Name:     Original filename:  ntdll.dll 

Module name:  ntdll   Private Build:   

Single Threaded:  False   Product Name:  Microsoft® Windows® Operating
System 

Module Size:  776.00 KBytes   Product Version:  5.2.3790.4455 

Symbol File Name:  ntdll.dll   Special Build:  &

------------------------------------------------------------------------


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/bug.php?id=53292


-- 
Edit this bug report at http://bugs.php.net/bug.php?id=53292&edit=1

Reply via email to