It gets weirder... my first attempt with -g froze the X server somehow yesterday (which I should have mentioned in the report) and occasionally I'm seeing this behavior even when I think it's not trying to get to gmail, just the "Grand Paradiso" start page or even a blank page, and -safe-mode doesn't seem to prevent that. I've seen this a bit before, but I thought I'd left it trying to reload the tabs that had gmail somehow. There seems to be some saved state somewhere, too, since the behavior sometimes changes on reboot; I'll followup on that later so I can send this before reboot.
Anyway, it looks like the parent iceweasel wrapper process segfaults, taking gdb with it, but leaves xulrunner churning, detached from the tty as far as the shell and the debugger are concerned but with stdout still printing ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) forever... Also the debugger complains about missing debug symbols, although I seem to have the right things installed: ii iceweasel-dbg 3.0~rc2-2 ii xulrunner-1.9-dbg 1.9~rc2-4 here is a transcript and some notes: fix:~> iceweasel -g -P foo_test -safe-mode GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu"... (no debugging symbols found) (gdb) r Starting program: /usr/lib/iceweasel/firefox-bin -a firefox--foo_test -P foo_test -safe-mode (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) Executing new program: /usr/lib/xulrunner-1.9/xulrunner-stub [Thread debugging using libthread_db enabled] [New Thread 0x7f1361f2c6f0 (LWP 27161)] [New Thread 0x4233d950 (LWP 27179)] [New Thread 0x42b3e950 (LWP 27180)] [New Thread 0x4333f950 (LWP 27181)] [Thread 0x4333f950 (LWP 27181) exited] [New Thread 0x40e54950 (LWP 27183)] [Thread 0x40e54950 (LWP 27183) exited] [New Thread 0x40e54950 (LWP 27184)] [Thread 0x4233d950 (LWP 27179) exited] [Thread 0x40e54950 (LWP 27184) exited] [Thread 0x42b3e950 (LWP 27180) exited] [New process 27161] Executing new program: /usr/lib/xulrunner-1.9/xulrunner-stub warning: Cannot initialize thread debugging library: generic error warning: Cannot initialize thread debugging library: generic error warning: Cannot initialize thread debugging library: generic error warning: Cannot initialize thread debugging library: generic error [New process 27161] [Thread debugging using libthread_db enabled] Error while reading shared library symbols: Cannot find new threads: generic error /usr/bin/iceweasel: line 151: 27160 Segmentation fault "$@" fix:~> ******** at this point, the "safe mode" window is up, and the iceweasel wrapper script is done, but clearly something is still running. ******** fix:~> ps PID TTY TIME CMD 4043 pts/3 00:00:00 tcsh 27161 pts/3 00:00:01 xulrunner-stub 27255 pts/3 00:00:00 ps ******** if I say "continue in safe mode" it will (last time I tried) run with the problem as a background process, so I couldn't hit ctrl-c as you asked, 'cause the shell catches it. I tried sending SIGINT to the xulrunner-stub from another window via kill -INT 27161, which killed it, but didn't send it to gdb, which had apparently quit or been killed in the above segfault. I appear to have xulrunner-1.9 and xulrunner-1.9-dbg installed at 1.9~rc2-4 -- I'm not clear on how xulrunner is related to iceweasel; my impression is that xulrunner is now the underlying mozilla engine for firefox & friends, right? I could continue to flail around, but I think it'll be faster/easier to have your expert suggestions... Note that without the -g, I *can* use ctrl-c from the shell to interrupt it. For extra confusion, the segfault appears to be related to the debugger: fix:~> iceweasel -P foo_test -safe-mode >& iceweasel.out gives an iceweasel.out that starts with: ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) sh: acroread: command not found ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) I have no idea why it cares about acroread, since I tend to use evince or xpdf anyway, and I don't appear to have acroread installed at all. (So it's no shock that it's not found.) I'm going to send this, reboot, and try again, since I've been perplexed that rebooting seems to clear some state related to this sometimes... Sorry this is so complicated... - M On Wed, Jun 25, 2008 at 11:05 AM, Mike Hommey <[EMAIL PROTECTED]> wrote: > On Wed, Jun 25, 2008 at 01:35:53AM -0700, Mark Montague wrote: >> Package: iceweasel >> Version: 3.0~rc2-2 >> Severity: normal >> >> iceweasel hangs printing >> >> ** Message: GetValue variable 1 (1) >> ** Message: GetValue variable 2 (2) >> >> using -safe-mode doesn't help, nor does using a new profile nor removing >> plugins, nor clearing cookies & sessions. > > Can you install gdb and iceweasel-dbg, run iceweasel -g, type run, then get it > to hang, press ctrl+c in the gdb terminal, then type bt full and send > the output here ? > > Thanks > > Mike > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
