On Sun, 7 Jan 2007, Eric Dorland wrote:

> * Justin Piszcz ([EMAIL PROTECTED]) wrote:
> > Package: firefox
> > Version: 1.5.dfsg+1.5.0.7-1
> > 
> >     * The exact and complete text of any error messages printed or logged. 
> > This is very important!
> > 
> > When browsing various websites, both ones that use plugins and not, 
> > firefox crashes and leaves 150-200MB core files.  The bottom of this 
> > e-mail contains a backtrace.
> > 
> >     * Exactly what you typed or did to demonstrate the problem.
> > One thing that I like to do is right click an RSS feed and say open in 
> > tabs, to view a lot of information at once, this can also trigger a crash.
> > 
> >     * A description of the incorrect behaviour: exactly what behaviour you 
> > were expecting, and what you observed. A transcript of an example session 
> > is a good way of showing this.
> > I was expecting the browser to be stable and not crash.  The official 
> > verison from ftp.mozilla.org does not have such problems.
> > 
> >     * A suggested fix, or even a patch, if you have one.
> > Will Debian ever consider using the official firefox build?  I've had a 
> > similar bug in the past, one which was easily reproduced but it never got 
> > resolved.
> 
> We can't just use the official build, everything in debian needs to be
> built from source. Also there are several portability, bug and FHS
> fixes not in the mozilla version. But largely they are exactly the
> same. 
>  
> >     * Details of the configuration of the program with the problem. 
> > Include the complete text of its configuration files.
> > Nothing special here, your standard list of plugins and such, which were 
> > used in both Debian's Firefox and the official version.
> > 
> >     * The versions of any packages on which the buggy package depends.
> > None available.
> > 
> >     * What kernel version you're using (type uname -a), your shared C 
> > library (type ls -l /lib/libc.so.6 or dpkg -s libc6 | grep ^Version), and 
> > any other details about your Debian system, if it seems appropriate. For 
> > example, if you had a problem with a Perl script, you would want to 
> > provide the version of the `perl' binary (type perl -v or dpkg -s perl | 
> > grep ^Version:).
> > # uname -a
> > Linux box 2.6.17.13 #6 SMP PREEMPT Sat Nov 4 13:48:54 EST 2006 i686 
> > GNU/Linux
> > lrwxrwxrwx 1 root root 13 2006-11-04 06:13 /lib/libc.so.6 -> 
> > libc-2.3.6.so*
> > # dpkg -s libc6 | grep ^Version
> > Version: 2.3.6.ds1-7
> > 
> >     * Appropriate details of the hardware in your system. If you're 
> > reporting a problem with a device driver please list all the hardware in 
> > your system, as problems are often caused by IRQ and I/O address 
> > conflicts. 
> > CPU: 2.6GHZ P4
> > RAM: 2GB
> > SWAP: 2GB
> > 
> > Backtrace:
> > $ du -sh core*
> > 146M    core.1746
> > 192M    core.2070
> > 
> > $ file core*
> > core.1746: ELF 32-bit LSB core file Intel 80386, version 1 (SYSV), 
> > SVR4-style, from 'firefox-bin'
> > core.2070: ELF 32-bit LSB core file Intel 80386, version 1 (SYSV), 
> > SVR4-style, from 'firefox-bin'
> > 
> > (gdb) bt
> > #0  0xb7df74e8 in raise () from /lib/tls/libpthread.so.0
> > #1  0x080829cc in ?? ()
> > #2  0x0000000b in ?? ()
> > #3  0xbfd278a0 in ?? ()
> > #4  0x00000000 in ?? ()
> > (gdb) 
> > 
> > (gdb) bt
> > #0  0xb7dad518 in raise () from /lib/tls/libpthread.so.0
> > #1  0x080829cc in ?? ()
> > #2  0x0000000b in ?? ()
> > #3  0xbfece550 in ?? ()
> > #4  0x00000000 in ?? ()
> > (gdb) 
> 
> Can you install the iceweasel-dbg package and then do a backtrace to
> get better symbols.
Yeah, I can install iceweasel and see if the problem occurs again; if so, 
I will do that and get back to you with the symbols.
> 
> Where exactly are you getting these questions from?
Submitting a bug report for Debian I believe.
>  
> 
> -- 
> Eric Dorland <[EMAIL PROTECTED]>
> ICQ: #61138586, Jabber: [EMAIL PROTECTED]
> 1024D/16D970C6 097C 4861 9934 27A0 8E1C  2B0A 61E9 8ECF 16D9 70C6
> 
> 


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

Reply via email to