firefox core dumps in ubuntu

RESOLVED INCOMPLETE

Status

()

Firefox
General
--
critical
RESOLVED INCOMPLETE
9 years ago
9 years ago

People

(Reporter: manusha1980, Unassigned)

Tracking

3.0 Branch
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (compatible; Konqueror/4.1; Linux) KHTML/4.1.3 (like Gecko)
Build Identifier: 3.0.5

when invoked from terminal (firefox), it coredumps. here is the stack trace for all threads.


Thread 4 (process 5223):
#0  0xb7f0f430 in __kernel_vsyscall ()
#1  0xb7d15f77 in ?? ()
#2  0xb7b83d8c in ?? ()
#3  0xb7152a7b in ?? ()
#4  0xb7152f70 in ?? ()
#5  0xb715321a in ?? ()
#6  0xb78a750e in ?? ()
#7  0xb7877f88 in ?? ()
#8  0xb7152c93 in ?? ()
#9  0xb78a756c in ?? ()
#10 0xb7877f88 in ?? ()
#11 0xb78a7cd3 in ?? ()
#12 0xb7b881e1 in ?? ()
#13 0xb7ecc50f in ?? ()
#14 0xb7d207ee in ?? ()

Thread 3 (process 5224):
#0  0xb7f0f430 in __kernel_vsyscall ()
#1  0xb7ed03a2 in ?? ()
#2  0x16bc7ee0 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 2 (process 5227):
#0  0xb7f0f430 in __kernel_vsyscall ()
#1  0xb7ed03a2 in ?? ()
#2  0x1d0b68d8 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 1 (process 5221):
#0  0xb7f0f430 in __kernel_vsyscall ()
#1  0xb7ed44c0 in ?? ()
#2  0xb70faca1 in ?? ()
#3  <signal handler called>
#4  0xb7303ab3 in ?? ()
#5  0xb73a0a12 in ?? ()
#6  0xb744252d in ?? ()
#7  0xb744323b in ?? ()
#8  0xb744378d in ?? ()
#9  0xb71f4f5e in ?? ()
#10 0xb720c202 in ?? ()
#11 0xb720d034 in ?? ()
#12 0xb720e6e1 in ?? ()
#13 0xb720ecbd in ?? ()
#14 0xb7207d10 in ?? ()
#15 0xb71f3771 in ?? ()
#16 0xb71f3f99 in ?? ()
#17 0xb71fedc5 in ?? ()
#18 0xb7201240 in ?? ()
#19 0xb71fef20 in ?? ()
#20 0xb7388437 in ?? ()
#21 0xb78b33f9 in ?? ()
#22 0xb7120853 in ?? ()
#23 0xb7127e55 in ?? ()
#24 0xb7bead35 in ?? ()
#25 0xb7bdebfc in ?? ()
#26 0xb7bead84 in ?? ()
#27 0xb711d9d1 in ?? ()
#28 0xb71192ed in ?? ()
#29 0xb78b3f04 in ?? ()
#30 0xb78b33f9 in ?? ()
#31 0xb7120853 in ?? ()
#32 0xb7127e55 in ?? ()
#33 0xb7bead35 in ?? ()
#34 0xb7bdebfc in ?? ()
#35 0xb7bead84 in ?? ()
#36 0xb711d9d1 in ?? ()
#37 0xb71192ed in ?? ()
#38 0xb78b3f04 in ?? ()
#39 0xb70f530b in ?? ()
#40 0x080491ab in ?? ()
#41 0xb7c55685 in ?? ()
#42 0x08048d11 in ?? ()




Reproducible: Always

Steps to Reproduce:
1.
2.
3.



im using the ubuntu 8.10.

Comment 1

9 years ago
That's not a usable stack trace. Will need one with symbols.
http://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report
Either use the official build to get a crash ID or follow the Ubuntu specific instructions linked to at the bottom.
https://wiki.ubuntu.com/MozillaTeam/Bugs#Obtain%20a%20backtrace%20from%20an%20apport%20crash%20report%20%28using%20gdb%29
Version: unspecified → 3.0 Branch

Comment 2

9 years ago
Resolving as incomplete as the bug reporter has not commented after a suggestion was provided in comment #1.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.