Hi there,

I recently ported my browser embedded app from mozilla0.9.0-based to
0.9.4-based. I built the release with debug info.
However, I found that calling mozilla APIs from my app resulted in
calling wrong APIs. For example, when my app called on
document->GetScriptableGlobalObject, the system threw the assertion. I
then stepped into the breakpoint and found
InsertStyleSheetAt (in nsDocument) got called instead of
document->GetScriptableGlobalObject. It seems to me that
the system looked into wrong APIs at runtime. Such API calls was ok with
0.9.0 libraries. Did anyone have such porting problem before?


Thanks

begin:vcard 
n:;
x-mozilla-html:FALSE
adr:;;;;;;
version:2.1
note;quoted-printable:-------------=0D=0AThis e-mail is solely for the use of the intended recipient and may=0D=0Acontain information which is confidential or privileged. Unauthorised=0D=0Ause of its contents is prohibited. If you have received this e-mail in=0D=0Aerror, please notify the sender immediately via return e-mail and then=0D=0Adelete the original e-mail.
x-mozilla-cpt:;-2080
end:vcard

Reply via email to