From: Rodolphe Rocca <fake2@free.fr>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] How can I capture enough debug info to make a good bug report?
Date: Tue, 02 Oct 2007 17:35:20 +0200 [thread overview]
Message-ID: <47026538.9020802@free.fr> (raw)
In-Reply-To: <5bdc1c8b0710020704n77031734hc5cb2a24719d8d3d@mail.gmail.com>
Mark Knecht wrote:
> Hi,
> On a subscriber web site I am seeing a consistent problem with both
> Firefox & Firefox-bin. When I click a specific link the browser
> crashes with a seg fault:
>
> mark@lightning ~ $ firefox-bin
> No running windows found
> /usr/libexec/mozilla-launcher: line 119: 6108 Segmentation fault
> $(type -P aoss) "$mozbin" "$@"
> firefox-bin exited with non-zero status (139)
> mark@lightning ~ $ firefox
> No running windows found
> Removing /home/mark/.mozilla/firefox/ipm4osof.default/compreg.dat
> leftover from older firefox
> /usr/libexec/mozilla-launcher: line 119: 6149 Segmentation fault
> $(type -P aoss) "$mozbin" "$@"
> firefox-bin exited with non-zero status (139)
> mark@lightning ~ $
>
> Note that I see Firefox crashing on my Windows Vista box also, but
> Internet Explorer does not, so this doesn't seem to me to be a Linux
> issue specifically.
>
> How can I get enough info to pass along to someone and have it be useful?
>
1) Remerge firefox with the debug use flag
2) rebuild your kernel (if needed) with CONFIG_ELF_CORE=y
3) reboot
4) connect your page
The segfault should produce a core file that you could send to firefox devs.
If I forgot something, guys, please correct me.
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2007-10-02 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 14:04 [gentoo-amd64] How can I capture enough debug info to make a good bug report? Mark Knecht
2007-10-02 15:23 ` Beso
2007-10-02 16:39 ` Mark Knecht
2007-10-02 15:35 ` Rodolphe Rocca [this message]
2007-10-02 16:43 ` Mark Knecht
2007-10-02 18:41 ` Beso
2007-10-02 15:56 ` Ângelo Miguel Arrifano
2007-10-02 16:10 ` Rodolphe Rocca
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47026538.9020802@free.fr \
--to=fake2@free.fr \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox