Closed
Bug 526991
Opened 15 years ago
Closed 15 years ago
"make -s -C mail" causes app to segfault [Regression]
Categories
(Thunderbird :: Build Config, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 525481
People
(Reporter: BenB, Unassigned)
Details
(Keywords: crash, regression)
- Linux - TB trunk Reproduction: 1. Fetch a fresh c-c (trunk) 2. Build it 3. Start the build 4. make -s -C mail (in build dir) 5. Start the build 6. make -s 7. Start the build Actual result: Step 3 and 7 work Step 5 fails with a segfault Expected result: Step 3, 5 and 7 all work (the same) Severity: Critical (crash) Blocker. Any tiny change I make to chrome needs a "make" (I don't bother with plain files chrome). "make -s -C mail" takes ~5s, "make -s" takes ~1min. Given that I do that *all the time*, this is disruptive for development. => Blocker
Reporter | ||
Comment 1•15 years ago
|
||
It's also a regression: It worked 1-2 weeks ago.
Keywords: regression
Summary: "make -s -C mail" causes sugfault → "make -s -C mail" causes sugfault [Regression]
Reporter | ||
Updated•15 years ago
|
Summary: "make -s -C mail" causes sugfault [Regression] → "make -s -C mail" causes segfault [Regression]
Reporter | ||
Comment 2•15 years ago
|
||
Sorry, with "Start the build", I meant to start the application, i.e. ./mozilla/dist/bin/thunderbird
Reporter | ||
Updated•15 years ago
|
Summary: "make -s -C mail" causes segfault [Regression] → "make -s -C mail" causes app to segfault [Regression]
Reporter | ||
Comment 3•15 years ago
|
||
Actually, even after make -s, the first app start works, but the second segfaults. Without any make -s -C mail involved. I did a diff -urw of the mozilla/dist/bin/, and they were identical before first, second and third start. After make -s -C mail of course changed 2 jar files, but nothing else. So, it's *not* the build system. I deleted XUL.mfasl, and that fixed it. Oh how I hate this XUL.mfasl and xpti.dat. Compare bug 525154. INVALID
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•