382099 - Socorro processor not pointing at symbols paths

Status: RESOLVED FIXED

(mozilla.org Graveyard :: Server Operations, task)

Description

[(not currently active) Ted Mielczarek]

The crash reports in Socorro currently don't seem to be using any of the debug symbols.  This makes the stack traces pretty much useless.  The processor needs to be pointing at the symbols_ffx and symbols_os directories (/mnt/netapp/breakpad/symbols_ffx/ on stage) to get the proper symbols.  sayrer can point you to the proper place to configure this.

Comment 1

[Benjamin Smedberg]

This would be in:

dist/processor/socorro/lib/config.py

processorSymbols = ["/mnt/netapp/breakpad/symbols_ffx",
                    "/mnt/netapp/breakpad/symbols_os"]

Comment 2

[Aravind Gottipati [:aravind]]

Fixed it.  I only had the top level symbols directory.  just as a note, I changed the symbols nfs share to the newer netapp.

Also, I am seeing these errors ever so often in the processor logs now.

2007-05-26 01:31:12: minidump.cc:787: ERROR: MinidumpMemoryRegion request out of range: 0x3d8fe0+4/0x152fe10+0x1f0
2007-05-26 01:31:12: minidump.cc:787: ERROR: MinidumpMemoryRegion request out of range: 0x3da41c+4/0x152fe10+0x1f0
2007-05-26 01:31:12: minidump.cc:787: ERROR: MinidumpMemoryRegion request out of range: 0x602fc564+4/0x152fe10+0x1f0
2007-05-26 01:31:12: minidump.cc:787: ERROR: MinidumpMemoryRegion request out of range: 0x3da3f8+4/0x152fe10+0x1f0


Didn't know if they matter, but listing them here anyway.

Comment 3

[Benjamin Smedberg]

That's within ordinary operation. It probably means that we're missing some symbols, but that's to be expected.