On Fri, Apr 07, 2006 at 01:43:21PM +0200, Bert Verbeek wrote:
> On Thursday 06 April 2006 23:10, you wrote:
> > strace -s99 -ff -o/tmp/firefox-strace -p
> 
> Hello Justin,
> 
> I send you this mail privately without sending a copy to the 
> [EMAIL PROTECTED] adress. It will get too messy, I think.
Huh?  WHy?

> It is getting stranger and stranger ... 
> 
> I did the following to find out wether I missed some files in /tmp you asked 
> for, I thought I only saw one, not more for every thread, as you said.
> 
> First I checked in my history file if I used -ff to the trace command. I did, 
> then:
> 
> ps aux | grep firefox
> 
> -------------
> bert     14125  2.7  2.5  98236 26564 ?        Sl   13:14 
> 0:01  /usr/lib/firefox/firefox-bin -a firefox
> bert     14157  0.0  0.0   1952   632 pts/3    S+   13:15   0:00 grep firefox
> -------------
> 
> strace -s99 -ff -o/tmp/firefox-strace -p 14125
> 
> placed my mouse over the firefox window to input some keystrokes, then strace 
> aborted directly with:
> 
> ----
> Process 14138 attached with 4 threads - interrupt to quit
> Process 14138 detached
> Process 14125 detached
> Process 14134 detached
> *** glibc detected *** double free or corruption (top): 0x0807b5d0 ***

> -----
> 
> only one file in /tmp which reads,
I really don't understand this; you're strace output is all garbled,
and perhaps has all the threads into a single file...

Please also try the strace with:

  G_SLICE=always-malloc strace -s99 -ff -o/tmp/firefox-strace -p (firefoxPid)

and see if it still aborts; if it does, then try now to get a
backtrace when it aborts, by getting a core file by setting ulimit -c
unlimited, and then running gdb /usr/lib/firefox/firefox-bin ./core
(assuming the file is called just "core").

> I'm willing to spend more time in this problem, but numerous things can be 
> tested from here on. Is it a good idea I first set up a fresh Debian testing 
> release installation on a spare disk partition? and test it further from 
> there?
You might do that, or just the chroot idea I suggested.

Justin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to