Re: GoogleEarth segfault [SOLVED]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


On Tue, Mar 2, 2010 at 3:17 PM, Matthew Saltzman <[email protected]> wrote:
> It all came down to missing i686 libs:

If those libraries were linked the normal way, by having set
them up when Google Earth launched, the missing libraries would have
prevented it from launching at all.  You wouldn't have gotten any kind
of crash, it just wouldn't execute.

My guess is that the missing libraries are normally loaded "manually,"
that is, with some of Google Earth's own code calling the dynamic
library manipulation functions and setting up the link itself.  That's
usually done to enable one to choose one of several alternative
libraries, or to add extra features that don't come built in.  Native
web browser plugins are handled that way too.

If that were the case, quite likely the reason that you got the
segfault is that that manual link failed completely because the
libraries were not to be found, but with the client code that expected
those libraries to be linked failing to check if the library load was

If my theory is correct, then Google needs a bug report.  I don't have
a clue how you'd file one.  But then, as they say, WHAT NOW is your

Don Quixote
Don Quixote de la Mancha
[email protected]

   Dulcinea Technologies Corporation: Software of Elegance and Beauty.
users mailing list
[email protected]
To unsubscribe or change subscription options:

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux