Comment 11 for bug 217032
Revision history for this message
|
|
#11 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
you're kidding, right?
the first bug you linked to is an invalid mess. and you managed to link to the same report twice. hint: don't link to more than one external report, and if the report is invalid, it's probably not something you want qa to read, so don't bother linking at all.
#3 <signal handler called>
^ this is when you crashed. the stuff past this point is just cleanup so that you can run firefox again.
fwiw, your attachment is almost useful, except it's missing the critical bits:
No symbol table info available.
#4 0xb6dde63b in ?? () from /usr/lib/
No symbol table info available.
#5 0xb7c1d50a in ?? () from /usr/lib/
please install the -dbg packages for these libraries. then get a new stack trace.
fwiw, we don't generally have a use for an strace. we need a complete and valid stack trace. these come from things like debuggers such as gdb. however, in order for them to be able to give you a good stack trace, they need debugging symbols. information on installing those symbols (from -dbg packages on your platform) can be obtained from your distro vendor.
as it happens, your vendor even has a wiki page specifically for this product, and it's in one of the bugs you linked to. in general it's a good idea to read things you want others to read....
https:/
note that had you read that wiki you'd at least have symbols for nspr. sadly for unknown reasons they don't tell you to install symbols for cairo. please feel free to kindly suggest to them that they add it to the list. (you should really have symbols for: x, glib, gdk, and cairo in addition to the ones they list.)