Re: [gentoo-amd64] How can I capture enough debug info to make a good bug report?

[Rodolphe Rocca <fake2@free.fr>]

Ângelo Miguel Arrifano wrote:
> On Tue, 2 Oct 2007 07:04:42 -0700
> "Mark Knecht" <markknecht@gmail.com> 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?
>>
>> Thanks,
>> Mark
>> -- 
>> gentoo-amd64@gentoo.org mailing list
>>
>>     
>
> You can also look at this guide:
> http://www.gentoo.org/proj/en/qa/backtraces.xml [gentoo.org]
>   
Cool, yet another very valuable work from diego !

I was wondering why I wasn't getting core files on my gentoo when I
found the "ulimit -c unlimited" command in this guide.

Now in my bookmarks !


-- 
gentoo-amd64@gentoo.org mailing list