On Wed, May 25, 2016 at 4:06 PM, Nicholas Nethercote
wrote:
>
> Do we have documentation on how to read crash reports?
I've finished a first pass at documentation on understanding
individual crash reports. The bulk of the effort was in writing this
new page: https://developer.mozill
On Thu, May 26, 2016, at 02:41 PM, Benoit Girard wrote:
> - Crash address can give you a hint as to what's going on: 0x0 -> null
> crash, 0x8 -> null offset accessing a member like this->mFoo,
N.B.: due to the way addressing works on x86-64, if the crash address is
"0x0" for a Linux/OS X crash rep
On Thu, May 26, 2016, at 09:52 AM, Benjamin Smedberg wrote:
> https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/Debugging_a_minidump
I spent some time today cleaning this page up a bit. I streamlined the
Windows section (since you no longer need to manually download the
matching binaries
en-US/docs/Mozilla/Debugging/Debugging_a_minidump
>
> --BDS
>
>
> On Wed, May 25, 2016 at 2:06 AM, Nicholas Nethercote <
> n.netherc...@gmail.com
> > wrote:
>
> > Hi,
> >
> > Do we have documentation on how to read crash reports? The only thing
> >
gging/Debugging_a_minidump
--BDS
On Wed, May 25, 2016 at 2:06 AM, Nicholas Nethercote wrote:
> Hi,
>
> Do we have documentation on how to read crash reports? The only thing
> I have found is this page:
>
> https://support.mozilla.org/en-US/kb/helping-crashes
>
> which is not bad, but is la
, so I filed bug 1275799.
On Wed, May 25, 2016 at 4:06 PM, Nicholas Nethercote
wrote:
> Hi,
>
> Do we have documentation on how to read crash reports? The only thing
> I have found is this page:
>
> https://support.mozilla.org/en-US/kb/helping-crashes
>
> which is not
Hi,
Do we have documentation on how to read crash reports? The only thing
I have found is this page:
https://support.mozilla.org/en-US/kb/helping-crashes
which is not bad, but is lacking some details. I suspect there is
quite a bit of crash report interpretation wisdom that is in various
7 matches
Mail list logo
