On Thu, Apr 06, 2006 at 10:20:41AM +0200, Bert Verbeek wrote: > On Tuesday 04 April 2006 19:29, Justin Pryzby wrote: > > The next time it happens, could you try to get a backtrace of > > the process, and the output of: > > > > strace -s99 -ff -o/tmp/firefox-strace -p (firefoxPid) > > > > while you hit some keys? > > terminal response: > > ---------------------- > strace -s99 -ff -o/tmp/firefox-strace -p 7518 > Process 7536 attached with 5 threads - interrupt to quit > ---------------------- > > I keyed in "bverbeek" in some login window. > Response after quiting firefox by the window button: > > ---------------------- > Process 7536 detached > /tmp/firefox-strace: Bad file descriptor > /tmp/firefox-strace: Bad file descriptor > Process 7530 detached > *** glibc detected *** double free or corruption (!prev): 0x0807b5d0 *** > Aborted > ---------------------- Weird. I wonder if that is a strace bug ?!
Let me make sure I understand this. Your original problem is that firefox doesn't accept keybord input. When you strace it, you don't notice anything else happening differently, until you close firefox, at which point you get a bad FD error which you don't get when not stracing, and a glibc error which you also don't get? Can you retry the strace with: G_SLICE=always-malloc strace -s99 -ff -o/tmp/firefox-strace -p (firefoxPid) I am thinking that firefox may suffer from the problem noted in #357509, for which this is a workaround. It would be interesting if you could get a backtrace of this; try setting ulimit -c (bash specific) before the strace (or whatever is the simplest recipe for causing the abort). BTW, strace -ff should give multiple files; one per thread; please send all of them. If you're concerned about privacy or size of the bookmark strace, then just use a new user for this, and clear their bookmarks first. Could you also include the output of: ls -l /proc/(firefox pid)/fd/ immediately before starting the strace, and perhaps also the output of lsof -p (firefox pid)? It would also be interesting if you could try running the firefox process in a chroot; this is made pretty easy with debootstrap; check the examples in the manpage. You'll have to make sure that DISPLAY remains exported, but I don't think it will go away.. If that still fails (or even if it doesn't), you could also send a process list (ps -ef or whatever). Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
