Closed Bug 520852 Opened 15 years ago Closed 15 years ago

some mac XUL.sym files are empty except for a module line

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: ted, Assigned: ted)

References

(
URL
)

Details

See URL for an example. Not sure when this started happening, but it's obviously bad.
Regression range between those two nightlies: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=0a7dd88dbe67&tochange=9871bc47451f My fix from bug 520141 looks suspicious, of course.
I don't see any obvious way it could be responsible, but I'll keep looking.
Assignee: nobody → ted.mielczarek
Just for additional info, if I grab the .dSYM file: http://symbols.mozilla.org/firefox/XUL/751AC089442DA14C4350811DC23B50F90/XUL.dSYM.tar.bz2 and run dump_syms on it, I get just the MODULE line for i386, but full symbols for ppc. Running `file` on it gives: /XUL.dSYM/Contents/Resources/DWARF/XUL: Mach-O universal binary with 2 architectures ./XUL.dSYM/Contents/Resources/DWARF/XUL (for architecture ppc7400): Mach-O filetype=10 ppc ./XUL.dSYM/Contents/Resources/DWARF/XUL (for architecture i386): which is suspicious.
I apparently can't reproduce this on a universal build on my machine. The x86 XUL.sym looks fine.
And yesterday's nightly looks ok: http://symbols.mozilla.org/firefox/firefox-3.7a1pre-Darwin-20091007093342-symbols.txt http://symbols.mozilla.org/firefox/XUL/917FFDBFB7B1A67ACBEC350D69240ED70/XUL.sym I'm going to assume this was some temporary build machine problem. I'll reopen if it reoccurs.
Status: NEW → RESOLVED
Closed: 15 years ago
Component: Breakpad Integration → Release Engineering
Product: Toolkit → mozilla.org
QA Contact: breakpad.integration → release
Resolution: --- → INCOMPLETE
Version: Trunk → other
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.