Some libxul addresses are never resolved in crash stacks/signatures

RESOLVED INCOMPLETE

Status

()

--
major
RESOLVED INCOMPLETE
7 years ago
7 years ago

People

(Reporter: kairo, Unassigned)

Tracking

({regression})

unspecified
regression
Points:
---

Firefox Tracking Flags

(firefox12-)

Details

(Reporter)

Description

7 years ago
bug 711973 is filed on a skiplist addition in Socorro but the underlying problem is that a number of libxul.so/xul.dll/XUL addresses in stacks/signatures are not resolved to proper (function) names.

Judging from comments in e.g. bug 715916, but also general observation, this seems to be a regression, apparently somewhere between 11 and 12 (or probably somewhere in the 12 trunk timeframe).

This makes crash analysis pretty hard in some cases and has an especially large impact on native Android builds, it seems, so we should try to get this investigated and resolved ASAP.
(Reporter)

Updated

7 years ago
tracking-firefox12: --- → ?

Updated

7 years ago
Blocks: 717531
I think it's a dupe of bug 559661 that depends on bug 528092.
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #0)
> This makes crash analysis pretty hard in some cases and has an especially
> large impact on native Android builds, it seems, so we should try to get
> this investigated and resolved ASAP.

Does this continue to affect crash analysis?
Naoki: I think there's a big difference between what this was originally reported about, which AFAICT was "there are a few frames in a crash report with xul@address", vs. "there are no symbols for libxul at all in this report", which is what those two look like. If you're seeing a high incidence of crash reports like that, please file a new bug and we'll look into it. If it's just a few scattered reports then it might just be people using tinderbox builds or self builds that we don't have symbols for.
Ted - based on comment 5, should this be tracked against ff12?
I suspect the xul.dll ones are related to bug 726570. I'm not sure about the non-Windows ones, but it's possible that they're just stackwalking issues as well. it's really hard to say without examining individual reports.
Looking at a few of the mobile crashes, it looks like it might be a similar issue. Most likely it's just bug 697301.
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #0)
> This makes crash analysis pretty hard in some cases and has an especially
> large impact on native Android builds, it seems, so we should try to get
> this investigated and resolved ASAP.

If the impact is most noticeable for Native builds, we're not shipping them off of FF12 so no need to track for that release. Please re-nominate if this bug is getting in the way of desktop crash analysis.
tracking-firefox12: ? → -
This bug as filed isn't really fixable or useful. If you have particular crash reports or patterns of crash reports which are showing incorrect results, please file them specifically. Note that a set of Windows stackwalking issues were fixed in production yesterday.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.