Felipe, what you did in giving firefox backtrace is almost complete, but it still does not provide useful information yet. I think you don't need to issue "continue", but rather you need to follow step 6 in the wiki page that you mentioned. The output can be long; so you might want to issue:
set logging file /tmp/gdb.log
set logging on
(/tmp/gdb.log can be replaced by another file name of your choice)
before doing the backtrace dump. Then publish the /tmp/gdb.log to this bug database. The backtrace info is what the developers are after, I believe.
Felipe, what you did in giving firefox backtrace is almost complete, but it still does not provide useful information yet. I think you don't need to issue "continue", but rather you need to follow step 6 in the wiki page that you mentioned. The output can be long; so you might want to issue:
set logging file /tmp/gdb.log
set logging on
(/tmp/gdb.log can be replaced by another file name of your choice)
before doing the backtrace dump. Then publish the /tmp/gdb.log to this bug database. The backtrace info is what the developers are after, I believe.
Thx,
Wirawan