Chris Shen wrote:
> 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?
Excuse me if I'm stating the obvious here, but this sounds like a classic
header file mismatch problem. When you say you built the release, did you
mean you built the release of your app, or you built the Mozilla release?
I think you need to rebuild your app with the new 0.9.4 header files.
Cheers,
Bernie
