Mike Hommey wrote:
On Fri, Jan 29, 2010 at 01:21:04PM -0500, Gary Dale wrote:
Mike Hommey wrote:
On Fri, Jan 29, 2010 at 12:27:26PM -0500, Gary Dale wrote:
Mike Hommey wrote:
On Fri, Jan 29, 2010 at 11:49:11AM -0500, Gary Dale wrote:
Mike Hommey wrote:
On Fri, Jan 29, 2010 at 09:50:13AM -0500, Gary Dale wrote:
Mike Hommey wrote:
On Thu, Jan 28, 2010 at 05:55:32PM -0500, Gary Dale wrote:
Package: iceweasel
Version: 3.5.6-1
Severity: important

After Iceweasel crashes it refuses to restart - even in safe-mode -
until I reboot the computer. Simply logging out and back in again
doesn't clear the problem.
Does it say something when it refuses to restart ?

Isn't there a firefox-bin process still running ?

Mike

No. It just doesn't restart. There is no firefox-bin process
running. However syslog shows:

2010-01-29 09:49:16    transponder    kernel    [151666.119720]
firefox-bin[17244]: segfault at 0 ip (null) sp 00007fff546d4348
error 14 in xulrunner-stub[400000+15000]
Is there a ~/.mozilla/firefox/*/lock file ? What happens if you remove
it ?

Mike

Removing it doesn't help. That was the first thing I tried.
Can you send the output for strace -f -o /some/file iceweasel ?
(located, obviously, in /some/file, and, still obviously, when it fails,
only)

Cheers,

Mike

See attached:
19206 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
19206 +++ killed by SIGSEGV +++
Oh, segmentation fault.
Can you follow the instructions in /usr/share/bug/iceweasel/presubj to
get a backtrace ?

Thanks

Mike

Interesting. It doesn't crash when I run it with the -g option.
However, even after a normal shutdown from the -g mode, it still
won't restart.

Then can you try the following:
$ ulimit -c unlimited
$ iceweasel

That should give you a core file that you can give to gdb:
$ gdb /usr/lib/iceweasel/firefox-bin core

Mike

The screen output of bt full is:

(gdb) bt full
#0  0x0000000000000000 in ?? ()
No symbol table info available.
#1  0x00007fc9acb31e8d in open () from /usr/lib64/libartsdsp.so.0
No symbol table info available. #2 0x000000000040cd84 in ?? () No symbol table info available. #3 0x000000000040e525 in calloc () No symbol table info available. #4 0x00007fc9ac727360 in _dlerror_run (operate=0x7fc9ac7270b0 <dlsym_doit>, args=0x7fff7f010a10) at dlerror.c:142 result = 0x0 #5 0x00007fc9ac72707a in __dlsym (handle=<value optimized out>, name=<value optimized out>) at dlsym.c:71
       args = {handle = 0xffffffffffffffff, name = 0x7fc9acb32171 "open",
         who = 0x7fc9acb30dc5, sym = 0xffff8036534cdec0}
       result = 0x0
#6  0x00007fc9acb30dc5 in ?? () from /usr/lib64/libartsdsp.so.0
No symbol table info available.
#7  0x00007fc9acb31017 in access () from /usr/lib64/libartsdsp.so.0
No symbol table info available.
#8  0x0000000000402042 in ?? ()
No symbol table info available.
#9  0x00007fc9abec4abd in __libc_start_main (main=<value optimized out>,
argc=<value optimized out>, ubp_av=<value optimized out>, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff7f014d18)
   at libc-start.c:222
       result = <value optimized out>
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, 5312441944845273278, 4201824, 140735324179744, 0, 0, -5312158694417151810, -5320226610298533698}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x410da0, 0x7fff7f014d28},
           data = {prev = 0x0, cleanup = 0x0, canceltype = 4263328}}}
       not_first_call = <value optimized out>
#10 0x0000000000401d89 in ?? ()
No symbol table info available.
---Type <return> to continue, or q <return> to quit---
#11 0x00007fff7f014d18 in ?? ()
No symbol table info available.
#12 0x000000000000001c in ?? ()
No symbol table info available.
#13 0x0000000000000001 in ?? ()
No symbol table info available.
#14 0x00007fff7f0164c0 in ?? ()
No symbol table info available.
#15 0x0000000000000000 in ?? ()
No symbol table info available.
(gdb)


Is there something else I need to send you?




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to