[feisty] Firefox Crashed PPC

Taking to retrace

Oops, cannot retrace, I just noticed that is a ppc.

Kristoffer would you please run:

apport-retrace -s -d -C /tmp/ddebs 87656 > retrace.out

and upload the resulting retrace.out file

Tanks in advance.

Here's the content from retrace.out:

--- stack trace ---
#0 0x0fd6a8b0 in raise () from /lib/libpthread.so.0
#1 0x100119f4 in ?? ()
#2 <signal handler called>
#3 0x0fb3488c in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#4 0x0fb34884 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#5 0x0fb39ec8 in gtk_style_attach () from /usr/lib/libgtk-x11-2.0.so.0
#6 0x0fbfcfec in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#7 0x0fbfd204 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#8 0x0c3c0998 in ?? () from /usr/lib/firefox/components/libwidget_gtk2.so
#9 0x0f9fa984 in gtk_container_forall () from /usr/lib/libgtk-x11-2.0.so.0
#10 0x0f9b0064 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#11 0x0f9fa984 in gtk_container_forall () from /usr/lib/libgtk-x11-2.0.so.0
#12 0x0faff6b8 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#13 0x0fa68638 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#14 0x0f0aedd8 in ?? () from /usr/lib/libglib-2.0.so.0
#15 0x0f0b15d4 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#16 0x0f0b5278 in ?? () from /usr/lib/libglib-2.0.so.0
#17 0x0f0b56e4 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#18 0x0faa5f84 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#19 0x0c3cd9a8 in ?? () from /usr/lib/firefox/components/libwidget_gtk2.so
#20 0x0ce4bc20 in ?? () from /usr/lib/firefox/components/libtoolkitcomps.so
#21 0x10007e98 in ?? ()
#22 0x10003e78 in ?? ()
#23 0x0f444d40 in ?? () from /lib/libc.so.6
#24 0x0f444f98 in __libc_start_main () from /lib/libc.so.6
#25 0x00000000 in ?? ()
--- thread stack trace ---
.
Thread 11 (process 16633):
#0 0x0f4fa794 in poll () from /lib/libc.so.6
#1 0x0fdbdbf0 in PR_Poll () from /usr/lib/libnspr4.so
#2 0x0d4e77ac in ?? () from /usr/lib/firefox/components/libnecko.so
#3 0x0d4e824c in ?? () from /usr/lib/firefox/components/libnecko.so
#4 0x0feb5720 in ?? () from /usr/lib/firefox/libxpcom_core.so
#5 0x0fdc3224 in ?? () from /usr/lib/libnspr4.so
#6 0x0fd5f7e4 in start_thread () from /lib/libpthread.so.0
#7 0x0f505e84 in clone () from /lib/libc.so.6
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
.
Thread 10 (process 16634):
#0 0x0fd65614 in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/libpthread.so.0
#1 0x0fdba024 in ?? () from /usr/lib/libnspr4.so
#2 0x0fdbb154 in PR_WaitCondVar () from /usr/lib/libnspr4.so
#3 0x0feb8b28 in ?? () from /usr/lib/firefox/libxpcom_core.so
#4 0x0feb5720 in ?? () from /usr/lib/firefox/libxpcom_core.so
#5 0x0fdc3224 in ?? () from /usr/lib/libnspr4.so
#6 0x0fd5f7e4 in start_thread () from /lib/libpthread.so.0
#7 0x0f505e84 in clone () from /lib/libc.so.6
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
.
Thread 9 (process 16641):
#0 0x0fd65064 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1 0x0fdbb22c in PR_WaitCondVar () from /usr/lib/libnspr4.so
#2 0x0cb62198 in ?? () from /usr/lib/firefox/components/libstoragecomps.so
#3 0x0cb63918 in ?? () from /usr/lib/firefox/components/libstoragecomps.so
#4 0x0feb5720 in ?? () from /usr/lib/firefox/libxpcom_core.so
#5 0x0fdc3224 in ?? () from /usr/lib/libnspr4.so
#6 0x0fd5f7e4 in start_thread () from /lib/libpthread.so.0
#7 0x0f505e84 in clone () ...

Thank you for your feed back. Now this report has to be evaluated

seems not to be properly retraced. Are there -dbgsym packages for powerpc at all? Anyway, installing firefox-dbg might help a bit.

Kristoffer please run again

apport-retrace -s -d -C /tmp/ddebs 87656 > retrace.out

and upload the resulting retrace.out file

But before you have to tell apport where the debugging symbols packages repository is located by doing:

echo 'deb http://people.ubuntu.com/~pitti/ddebs feisty main universe' >> /etc/apt/sources.list && apt-get update

Thanks in advance.

Anyway I'm not sure at all if there are -dbgsym packages for powerpc

Thank you for the bug report however this report lacks information we need to investigate it further. Of course this is not your fault, but the retrace obtained from your report doesn't provide useful information for us as it seems to be corrupted. For this reason, we are now going to close the bug report - please feel free to reopen when you have more information at hand.

And please don't doubt to report any other crashes/issues you might have in the future.

Further information can be found at [1].

[1] https://wiki.ubuntu.com/MozillaTeam/Bugs