[th] firefox - analiza upadku...

[Paweł Sikora]

Program received signal SIGSEGV, Segmentation fault.
nsChromeRegistry::CheckForNewChrome (this=0x80be4f8) at 
nsChromeRegistry.cpp:1123
1123      manifestFileURL->GetFile(getter_AddRefs(manifest));


NS_IMETHODIMP
nsChromeRegistry::CheckForNewChrome()
{
  nsresult rv;

  PL_DHashTableEnumerate(&mPackagesHash, RemoveAll, nsnull);
  mOverlayHash.Clear();
  mStyleHash.Clear();
  mOverrideTable.Clear();

  nsCOMPtr<nsIURI> manifestURI;
  rv = NS_NewURI(getter_AddRefs(manifestURI),
           NS_LITERAL_CSTRING("resource:///chrome/app-chrome.manifest"));

  // this is the main manifest; if it doesn't exist we generate it from
  // installed-chrome.txt. When the build system learns about the new system,
  // this code can go away.

  nsCOMPtr<nsIFileURL> manifestFileURL (do_QueryInterface(manifestURI));
                       ^^^^^^^^^^^^^^^ NULL! patrz nizej.

  NS_ASSERTION(manifestFileURL, "Not a nsIFileURL!");

  nsCOMPtr<nsIFile> manifest;
  manifestFileURL->GetFile(getter_AddRefs(manifest));
  NS_ENSURE_TRUE(manifest, NS_ERROR_FAILURE);


Breakpoint 1, nsChromeRegistry::CheckForNewChrome (this=0x80be4f0) at 
nsChromeRegistry.cpp:1123
1123      manifestFileURL->GetFile(getter_AddRefs(manifest));

(gdb) info locals
rv = <value optimized out>
manifestURI = {
  <nsCOMPtr_base> = {
    mRawPtr = 0x8104048
  }, <No data fields>}
manifestFileURL = {
  <nsCOMPtr_base> = {
    mRawPtr = 0x0
  }, <No data fields>}
manifest = {
  <nsCOMPtr_base> = {
    mRawPtr = 0x0
  }, <No data fields>}
exists = -135455006
dirSvc = {
  <nsCOMPtr_base> = {
    mRawPtr = 0xffffbc98
  }, <No data fields>}
chromeML = {
  <nsCOMPtr_base> = {
    mRawPtr = 0xf7ee87bc
  }, <No data fields>}
next = {
  <nsCOMPtr_base> = {
    mRawPtr = 0x80c5488
  }, <No data fields>}


jak dla mnie, to jakis problem z liskiem, niz kompilatorem.