Closed Bug 903205 Opened 11 years ago Closed 6 years ago

crash stack trace addresses in libxul.so are not resolving to symbols in mochitest logs

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: karlt, Unassigned)

References

Details

https://tbpl.mozilla.org/php/getParsedLog.php?id=26321197&tree=Try&full=1#error0 Addresses in the firefox object are resolving to symbols (thread 0), but libxul.so addresses are not. Downloading the dist build, built with STRIP_FLAGS=--strip-debug, enables addr2line to pull out function names from libxul.so, showing that at least some of the symbols were good in the build. This log is for linux32 opt. (Haven't looked for crashes in other archs.)
libmozalloc.so address resolve fine in that log.
Blocks: 903225
try disabling elfhack?
Product: mozilla.org → Release Engineering
Blocks: 939610
How does this differ from bug 939610 ? Should we just dupe over there because it has more info & deps ?
This one is about a crash stacks, so not a duplicate of the assertion stack bug, and not a mochitest harness bug, I assume.
Summary: stack trace addresses in libxul.so are not resolving to symbols in mochitest logs → crash stack trace addresses in libxul.so are not resolving to symbols in mochitest logs
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
Component: General Automation → General
Blocks: 1517131
No longer blocks: 939610
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Let's leave this bug alone. What you're looking for is bug 1510574
Status: REOPENED → RESOLVED
Closed: 8 years ago → 6 years ago
Resolution: --- → INCOMPLETE
No longer blocks: 1517131
You need to log in before you can comment on or make changes to this bug.