[EDGY] firefox crashed [@??] [@??] [@??]

The file is attached.

Thanks for your bug report. Could you please install firefox-dbg and try to obtain a backtrace (or crash report) by following the instructions on https://wiki.ubuntu.com/DebuggingFirefox This will greatly aid us in tracking down your problem.

Which flash package do you have installed?
Which Java package do you have installed?
Which firefox extensions do you have installed?

Thanks
David

David,

Thanks for the reply. I will give it a shot. I'm pretty news to Linux
and Ubuntu so be patient with me please.

Charles

On Fri, 2006-12-08 at 22:04 +0000, David Farning wrote:

> Thanks for your bug report. Could you please install firefox-dbg and try
> to obtain a backtrace (or crash report) by following the instructions on
> https://wiki.ubuntu.com/DebuggingFirefox This will greatly aid us in
> tracking down your problem.
>
> Which flash package do you have installed?
> Which Java package do you have installed?
> Which firefox extensions do you have installed?
>
> Thanks
> David
>
> ** Description changed:
>
> + DistroRelease: Ubuntu 6.10
> + Package: firefox 2.0+0dfsg-0ubuntu3
> +
> I selected a link while viewing a website and Firefox became
> unresponsive then closed.
>
> ** Changed in: firefox (Ubuntu)
> Assignee: (unassigned) => David Farning
> Status: Unconfirmed => Needs Info
>

David,

I have firefox-dbg installed. I am not sure what I do next. I followed
the instructions on the following URL:

https://wiki.ubuntu.com/DebuggingFirefox

The following instructions were adhered to:

Obtaining a Backtrace
For Firefox, the procedure for obtaining a backtrace varies slightly
from the usual gdb program method. This is because firefox is actually a
shell script that starts the Firefox browser's binary.

The first step is to install the debugging symbols for firefox from the
main repository.

sudo aptitude install firefox-dbg

      * Then after closing all instances of Firefox, start Firefox from
        the terminal with the following command:

         firefox -g 2>&1 | tee gdb-firefox.log

      * Alternatively, you can also connect gdb to an already running
        Firefox process. First, you will need to obtain the PID for the
        running Firefox process as well as the full path to Firefox's
        binary:

         ps -o pid,command -C firefox-bin

        Then, connect gdb to the running Firefox process. For example,
        if the above command outputted:

         PID COMMAND
         15018 /usr/lib/firefox/firefox-bin -a firefox

        you would ignore the arguments passed to the command and run:

         gdb /usr/lib/firefox/firefox-bin 15018 2>&1 | tee gdb-firefox.log

After this, you should be in gdb. You can then set the break points you
need, cause firefox to crash, and obtain a backtrace. The output would
all be stored in gdb-firefox.log.

I get to the gdp command line in BASH byt entering this:

firefox -g 2>&1 | tee gdb-firefox.log

None of the additional commands get me anywhere. What am doing wrong?

Charles

On Fri, 2006-12-08 at 22:04 +0000, David Farning wrote:

> Thanks for your bug report. Could you please install firefox-dbg and try
> to obtain a backtrace (or crash report) by following the instructions on
> https://wiki.ubuntu.com/DebuggingFirefox This will greatly aid us in
> tracking down your problem.
>
> Which flash package do you have installed?
> Which Java package do you have installed?
> Which firefox extensions do you have installed?
>
> Thanks
> David
>
> ** Description changed:
>
> + DistroRelease: Ubuntu 6.10
> + Package: firefox 2.0+0dfsg-0ubuntu3
> +
> I selected a link while viewing a website and Firefox became
> unresponsive then closed.
>
> ** Changed in: firefox (Ubuntu)
> Assignee: (unassigned) => David Farning
> Status: Unconfirmed => Needs Info
>

Charles,

Thanks for getting back to us. It has been a busy couple of weeks. It looks likes we are able to get what we need to out your crash report.

Thanks
David

David,

Thanks for the good work. I'm sorry that I couldn't be more helpful. I'm
pretty new to Ubuntu and Linux. I'm a lot farther along now that I was
when you first contacted me. I hope that you had a nice holiday season.
Thanks again.

Charles

David Farning wrote:
> Charles,
>
> Thanks for getting back to us. It has been a busy couple of weeks. It
> looks likes we are able to get what we need to out your crash report.
>
> Thanks
> David
>
> ** Tags added: crash notsymbolized
>
>

Retrace done.

Extract from retraced stacktrace:
...
#3 <signal handler called>
#4 ?? ()
#5 ?? ()
#6 ?? ()
#7 ?? ()
#8 ?? ()
#9 ?? ()
...

Tagging as mt-confirm, mt-needtestcase for further processing

Retraced Thread Stacktrace

Thank you for the bug report however this report lacks information we need to investigate it further. Of course this is not your fault, but the coredump attached to your report doesn't provide useful information for us. For this reason, we are now going to close the bug report - please feel free to reopen when you have more information at hand.

And please don't doubt to report any other crashes/issues you might have in the future.

Further information can be found at [1].

[1] https://wiki.ubuntu.com/MozillaTeam/Bugs