Robert List wrote: > > Access violation - code c0000005 (first chance) > eax=028fde80 ebx=61126e8a ecx=028fcf68 edx=00000000 esi=0012f0fc edi=0012ef64 > eip=03050071 esp=0012ee18 ebp=0012ee5c iopl=0 nv up ei pl nz na po nc > cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00010206 > *** WARNING: Unable to verify checksum for C:\Programme\mozilla.org\Mozilla\nss3.dll > nss3!PK11_LookupCrls+1bc: > 03050071 8982a8000000 mov [edx+0xa8],eax ds:0023:000000a8=???????? > > # ChildEBP RetAddr Args to Child > 00 0012ee5c 0304fded 026f4428 0000000b 028fccf0 nss3!PK11_LookupCrls+0x1bc > 01 0012ee80 0305019a 026f4428 0012eeb4 020e51f0 nss3!PK11_TraverseSlot+0x84 > 02 0012ee9c 0304ff5c 0304fd69 0012eeb4 00000000 nss3!PK11_LookupCrls+0x2e5 > 03 0012eee4 03071751 028fccf0 ffffffff 00000000 nss3!PK11_LookupCrls+0xa7 > 04 0012ef04 60a319a4 026871a0 0012ef24 ffffffff nss3!SEC_LookupCrls+0x7e
Robert, I am having a hard time deciphering this stack. I don't know what the hexadecimal numbers after the function names mean (for example, the 0x1bc in PK11_LookupCrls+0x1bc). This stack seems to imply that PK11_LookupCrls calls itself, which contradicts the source code. So I think those hexadecimal numbers are important to understanding this stack. Could you drop in our debug DLLs (ftp://ftp.mozilla.org/pub/security/nss/releases/NSS_3_4_2_RTM/WIN954.0_DBG.OBJ/) into Mozilla 1.0 and see if you can get a stack trace with file names line numbers from the MSVC debugger? Thanks, Wan-Teh
