We don't get valid stack trace for: http://crash-stats.mozilla.com/report/index/c7116283-42c8-4e59-9690-83a4e2101217 despite debug symbols has been uploaded to /mnt/netapp/breakpad/symbols_fedora/. For example libxul.so (with hash F7901786B36A06AF3C13CA5CD485FBFC0) from crash report is present in /mnt/netapp/breakpad/symbols_fedora/libxul.so/F7901786B36A06AF3C13CA5CD485FBFC0 but symbol is not resolved in report.
Can someone verify that /mnt/netapp/breakpad/symbols_fedora/ is in the Socorro processor's symbol path in the config file?
Current path is: processorSymbolsPathnameList.default = "/mnt/socorro/symbols/symbols_ffx,/mnt/socorro/symbols/symbols_sea,/mnt/socorro/symbols/symbols_tbrd,/mnt/socorro/symbols/symbols_mob,/mnt/socorro/symbols/symbols_penelope,/mnt/socorro/symbols/symbols_sbrd,/mnt/socorro/symbols/symbols_camino,/mnt/socorro/symbols/symbols_os,/mnt/socorro/symbols/symbols_solaris,/mnt/socorro/symbols/symbols_opensuse" I don't see symbols_fedora in there. Should I add it?
Yes, please! If you can update staging as well while you're at it, that would be great.
Summary: No stack trace on crash-stats for Fedora builds → Add /mnt/netapp/breakpad/symbols_fedora/ to processorSymbolsPathnameList.default in Socorro config
I updated production and added it to the puppet configs, so staging will get the change as well as socorro in phx once it goes live. The staging change will update automatically within an hour. Productin is live now.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Jan, can you submit another crash and verify this bug is fixed?
Looks very good: http://crash-stats.mozilla.com/report/index/40a53d5e-1395-4b5d-88ab-8cc842101222 Thank you!
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.