Comment 53 for bug 226470

Erik, I'm working towards precisely what you ask. I am *almost* at the point where I have GDK turn on stack tracing after the first orphan window condition occurs. This is a *REAL* pain as it involves a callback from the GDK library which is written in C to the Mozilla stack trace code which is in C++ (I am learning things I really didn't want to have to learn about allowing C to call C++).

But getting a workable static debug variant of Firefox 3.0a2 is proving difficult (there are problems in the Mozilla cairo/pango code -- even the latest CVS sources refuse to compile).

I am making available the relatively static debugable Firefox 2.0 I managed to assemble at one point.

URL: http://www.aeiveos.com:8080/~bradbury/Firefox

Note the firefox-2.0d link.

This is a complete 2.0 install directory which does work for me (Firefox has some real problems if you don't give it a complete environment on startup -- but that is another bug).

At any rate you should note the firefox-bin file (which is the key component) at 139 MB (debugging doesn't come cheap...). If you do a ldd analysis on that firefox-bin you will see that it uses a limited set of system libraries. That is because almost all of the other libraries have been compiled into it having been compiled with debugging enabled. So if you choose to use it to diagnose the problem (since we seem to have it narrowed down to a mozilla / gtk / pthread / glib arena) it may be a useful.

Also please note, the downloads are going to be fed via a standard U.S. DSL line so ones use should be balanced.