Heres the stack trace for the problem. This happens when navigating to any 
site that supports https://

  ntdll.dll!7c901230()
  [Frames below may be incorrect and/or missing, no symbols loaded for 
ntdll.dll]
  nspr4.dll!PR_Assert(const char * s=0x023d7ad8, const char * 
file=0x023d7aa0, int ln=0x00000734)  Line 546 C
> nss3.dll!PK11_GetInternalSlot()  Line 1844 + 0x1d bytes C
  nss3.dll!PK11_TokenExists(unsigned long type=0x00000001)  Line 1897 + 0x5 
bytes C
  ssl3.dll!ssl3_config_match_init(sslSocketStr * ss=0x03223410)  Line 642 + 
0x39 bytes C
  ssl3.dll!ssl2_ConstructCipherSpecs(sslSocketStr * ss=0x03223410)  Line 206 
+ 0x9 bytes C
  ssl3.dll!ssl2_BeginClientHandshake(sslSocketStr * ss=0x03223410)  Line 
3007 + 0x9 bytes C
  ssl3.dll!ssl_Do1stHandshake(sslSocketStr * ss=0x03223410)  Line 149 + 0xf 
bytes C
  ssl3.dll!ssl_SecureSend(sslSocketStr * ss=0x03223410, const unsigned char 
* buf=0x030a6760, int len=0x00000196, int flags=0x00000000)  Line 1090 + 0x9 
bytes C
  ssl3.dll!ssl_SecureWrite(sslSocketStr * ss=0x03223410, const unsigned char 
* buf=0x030a6760, int len=0x00000196)  Line 1128 + 0x13 bytes C
  ssl3.dll!ssl_Write(PRFileDesc * fd=0x014075c8, const void * 
buf=0x030a6760, int len=0x00000196)  Line 1413 + 0x17 bytes C
  pipnss.dll!nsSSLThread::Run()  Line 919 C++
  nspr4.dll!_PR_NativeRunThread(void * arg=0x30023b3d)  Line 436 + 0x9 bytes 
C
  ntdll.dll!7c926a44()
  msvcr80d.dll!_callthreadstartex()  Line 348 + 0xf bytes C
  msvcr80d.dll!_threadstartex(void * ptd=0x0300cc70)  Line 331 C
  kernel32.dll!7c80b683()
  ntdll.dll!7c926a44()
PK11_GetInternalSlot() is returning null

For reference, here's my .mozconfig

mk_add_options MOZ_CO_PROJECT=browser
mk_add_options MOZ_OBJDIR=$topsrcdir/@CONFIG_GUESS@
ac_add_options --enable-application=browser
ac_add_options --disable-installer
ac_add_options --disable-static
ac_add_options --enable-shared
ac_add_options --enable-svg
ac_add_options --enable-crypto
ac_add_options --enable-debug
ac_add_options --disable-activex
ac_add_options --disable-activex-scripting

"timeless" <[EMAIL PROTECTED]> wrote in message 
news:[EMAIL PROTECTED]
> On Nov 20, 5:18 pm, "Jamie Newton" <[EMAIL PROTECTED]> wrote:
>> mfcembed crashes when navigating to an address starting https://. Is 
>> there a
>> fix for this problem?
>
> most likely it can't find the writable cert db files or perhaps it just
> can't find crypto.
>
> do you think you could provide a stack trace? gecko has lots of lines
> of code and predicting exactly where it will crash in an unspecified
> version of gecko (hint: please specify) is hard.
> 


_______________________________________________
dev-embedding mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-embedding

Reply via email to