Common Problems

  • Revision slug: Mozilla_Embedding_FAQ/Common_Problems
  • Revision title: Common Problems
  • Revision id: 181186
  • Created:
  • Creator: SylvainPasche
  • Is current revision? No
  • Comment /* <code>TestGTKEmbed</code> doesn't work! */

Revision Content

Section 4: Common Problems

TestGTKEmbed doesn't work!

Did you invoke it like this "./run-mozilla.sh ./TestGtkEmbed"? This script ensures the dynamic library paths are correct so that TestGtkEmbed can be loaded properly. Running TestGTKEmbed directly may result in the wrong Mozilla libs being picked up if you have other versions elsewhere (e.g. installed by Galeon / Nautilus etc.)

If you get the error message "Couldn't find a compatible GRE.", see how the GRE is located in GRE Registration. If you are running the build from dist/bin, you can simply invoke it with "GRE_HOME=. ./run-mozilla.sh ./TestGtkEmbed"

How do I build MFCEmbed?

By building Mozilla as per normal, ensuring not to specify the --disable-tests argument. The MS DevStudio mfcembed.dsp to be found in the mfcembed directory is for editing purposes only.

How do I debug MFCEmbed?

Two ways, either by using the mfcembed.dsp project file, or from a blank project in DevStudio. Obviously both are only useful if mfcembed & Gecko have been built with debugging enabled.

The mfcembed.dsp file is currently set up for editing purposes only. If you want to debug using mfcembed.dsp, you must open up the "Project | Settings..". menu and select Debug properties panel from the settings dialog. Provide the full path to the mfcembed.exe as it was built with the rest of Mozilla. e.g. c:\moz\mozilla\dist\bin\mfcembed.exe. It should then be possible to debug it.

Alternatively, open up a fresh Devstudio and drag and drop the mfcembed.exe from Mozilla dist onto it. Devstudio 7 doesn't allow you to drag and drop executables like this so you must manually open it using the file menu.

Most of the Gecko libraries are loaded dynamically at startup, so if you want to set breakpoints on them in Devstudio 6 you must select the Additional DLLs category in the Debug panel and add any DLLs you intend to put breakpoints on. Devstudio 7 manages to figure out the breakpoints automatically.

Why won't FTP work?

Make sure you are including the "necko2" DLL and XPT files. If you are able to download ftp files, but cannot show directories, you may be using the wrong FTP directory view. There are two different views to display FTP directories. One of these views is XUL-based and requires the "appcomps" DLL. The other view is HTML-based and requires only the necko2 DLL. The network.dir.generate_html preference will make mozilla use HTML mode.

There have been reports that appcomps.dll is still needed, even with HTML displays... this is a bug that needs to be investigated further. In fact, we should fallback to HTML if the directory viewer isn't found anyway. -alecf

Why is my build so huge?!

Mozilla does not use C++ exceptions, nor does it use run-time-type-info (RTTI). Building mozilla w/ these two options enabled on Linux using gcc 2.95.2, increases disk footprint by ~11Mb in a typical embedding scenario (exceptions taking up at least 90% of that added bloat). We strongly discourage the use of exceptions and RTTI. There is a bug in gcc for Linux that forces (you can't link w/ mozilla core) you to build mozilla w/ RTTI enabled if you are using exceptions in your code.

On Win32, I get a I get a dialog that says "The procedure entry point SEC_PKCS7CopyContentInfo could not be located in the dynamic link library smime3.dll"

This is related to a problem in the mozilla build faq. The solution is to look for the file nss3.dll in WINHOME/system32. Move aside or remove all files with the same modification date and time as that file.

Revision Source

<p>
</p>
<h2 name="Section_4:_Common_Problems"> Section 4: Common Problems </h2>
<h3 name="TestGTKEmbed_doesn.27t_work.21"> <code>TestGTKEmbed</code> doesn't work! </h3>
<p>Did you invoke it like this "./run-mozilla.sh ./TestGtkEmbed"? This script ensures the dynamic library paths are correct so that TestGtkEmbed can be loaded properly. Running TestGTKEmbed directly may result in the wrong Mozilla libs being picked up if you have other versions elsewhere (e.g. installed by Galeon / Nautilus etc.)
</p><p>If you get the error message "Couldn't find a compatible GRE.", see how the <a href="en/GRE">GRE</a> is located in <a href="en/GRE_Registration">GRE Registration</a>. If you are running the build from dist/bin, you can simply invoke it with "GRE_HOME=. ./run-mozilla.sh ./TestGtkEmbed"
</p>
<h3 name="How_do_I_build_MFCEmbed.3F"> How do I build MFCEmbed? </h3>
<p>By building Mozilla as per normal, ensuring not to specify the --disable-tests argument. The MS DevStudio mfcembed.dsp to be found in the mfcembed directory is for editing purposes only.
</p>
<h3 name="How_do_I_debug_MFCEmbed.3F"> How do I debug MFCEmbed? </h3>
<p>Two ways, either by using the mfcembed.dsp project file, or from a blank project in DevStudio. Obviously both are only useful if mfcembed &amp; Gecko have been built with debugging enabled.
</p><p>The mfcembed.dsp file is currently set up for editing purposes only. If you want to debug using mfcembed.dsp, you must open up the "Project | Settings..". menu and select Debug properties panel from the settings dialog. Provide the full path to the mfcembed.exe as it was built with the rest of Mozilla. e.g. c:\moz\mozilla\dist\bin\mfcembed.exe. It should then be possible to debug it.
</p><p>Alternatively, open up a fresh Devstudio and drag and drop the mfcembed.exe from Mozilla dist onto it. Devstudio 7 doesn't allow you to drag and drop executables like this so you must manually open it using the file menu.
</p><p>Most of the Gecko libraries are loaded dynamically at startup, so if you want to set breakpoints on them in Devstudio 6 you must select the Additional DLLs category in the Debug panel and add any DLLs you intend to put breakpoints on. Devstudio 7 manages to figure out the breakpoints automatically.
</p>
<h3 name="Why_won.27t_FTP_work.3F"> Why won't FTP work? </h3>
<p>Make sure you are including the "necko2" DLL and XPT files. If you are able to download ftp files, but cannot show directories, you may be using the wrong FTP directory view. There are two different views to display FTP directories. One of these views is XUL-based and requires the "appcomps" DLL. The other view is HTML-based and requires only the necko2 DLL. The <code>network.dir.generate_html</code> preference will make mozilla use HTML mode.
</p>
<div class="note">There have been reports that appcomps.dll is still needed, even with HTML displays... this is a bug that needs to be investigated further. In fact, we should fallback to HTML if the directory viewer isn't found anyway. -alecf</div>
<h3 name="Why_is_my_build_so_huge.3F.21"> Why is my build so huge?! </h3>
<p>Mozilla does <b>not</b> use C++ exceptions, nor does it use run-time-type-info (RTTI). Building mozilla w/ these two options enabled on Linux using gcc 2.95.2, increases disk footprint by ~11Mb in a typical embedding scenario (exceptions taking up at least 90% of that added bloat). We strongly discourage the use of exceptions and RTTI. There is a bug in gcc for Linux that forces (you can't link w/ mozilla core) you to build mozilla w/ RTTI enabled if you are using exceptions in your code.
</p>
<h3 name="On_Win32.2C_I_get_a_I_get_a_dialog_that_says_.22The_procedure_entry_point_SEC_PKCS7CopyContentInfo_could_not_be_located_in_the_dynamic_link_library_smime3.dll.22"> On Win32, I get a I get a dialog that says "The procedure entry point SEC_PKCS7CopyContentInfo could not be located in the dynamic link library smime3.dll" </h3>
<p>This is related to a problem in the mozilla build faq.  The solution is to look for the file <i>nss3.dll</i> in WINHOME/system32.  Move aside or remove all files with the same modification date and time as that file.
</p>
Revert to this revision