Issue 75883 - SRC680_m207: SIGSEGV during build in moz
Summary: SRC680_m207: SIGSEGV during build in moz
Status: CLOSED DUPLICATE of issue 74837
Alias: None
Product: porting
Classification: Code
Component: code (show other issues)
Version: 680m206
Hardware: All Windows Server 2003
: P3 Trivial (vote)
Target Milestone: ---
Assignee: quetschke
QA Contact: issues@porting
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2007-03-29 21:25 UTC by pavel
Modified: 2008-05-17 23:50 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description pavel 2007-03-29 21:25:12 UTC
...
mozilla/l10n/langpacks/Makefile.in
mozilla/l10n/makefile.win
mozilla/l10n/makefiles.all
mozilla/l10n/Makefile.in
make writeable...
Segmentation fault (core dumped)
dmake:  Error code 139, while making 'wntmsci10.pro/misc/build/so_unpacked_ooo_mozab'
dmake:  'wntmsci10.pro/misc/build/so_unpacked_ooo_mozab' removed.
---* tg_merge.mk *---

ERROR: Error 0 occurred while making /cygdrive/f/home/pavel/BuildDir/ooo_SRC680_m207_src/moz

Second issue like this in a row. Always after moz unpacking... Running dmake again manually helps. 
Running build in module moz helps too.

Building on Windows on my system gets me more and more nervous ;-)

I'm now starting m207 build for the third time to see if it crashes at the same place.
Comment 1 pavel 2007-03-30 12:00:29 UTC
Third build in row (after reboot): still the same crash in moz 8)
Comment 2 quetschke 2007-03-30 14:59:07 UTC
Issue assigned to me, oh well ...

Pavel, this doesn't happen for me, so lets find out what your system is like.

Can you send me your `cygcheck -svr > cygcheck.log`. Email, no need to attach it
here.

(I don't think that something is wrong in your setup, but let's dot all t's and
cross all i's.) 
Comment 3 pavel 2007-03-31 08:25:14 UTC
log sent.

I'm going back in the history to see where the problem started.

I uploaded m202 in the past, so am checking if it still builds here.
Comment 4 pavel 2007-03-31 16:40:58 UTC
So after weekend full of builds, I realized that m202 can be built completely without problems. m203 has 
various issues.

First candidate was ause074.

m202+ause074's dmake segfaulted in module accessibility in the first build. Second build of the same 
tree is now running.
Comment 5 pavel 2007-03-31 23:16:43 UTC
Second build of m202+ause074 end with:

... millions of Bad address messages...
chmod: cannot access `mozilla/xpinstall/wizard/windows/uninstall/uninstall.ico': Bad address
chmod: cannot access `mozilla/xpinstall/wizard/windows/uninstall/uninstall.rc': Bad address
dmake:  Error code 1, while making 'wntmsci10.pro/misc/build/so_unpacked_ooo_mozab'
dmake:  'wntmsci10.pro/misc/build/so_unpacked_ooo_mozab' removed.
---* tg_merge.mk *---

ERROR: Error 0 occurred while making /cygdrive/f/home/pavel/BuildDir.m202/ooo_SRC680_m202_src/
moz

The next build will be clean m202 again to see it it really builds. No reboot between both builds...
Comment 6 pavel 2007-04-01 14:02:17 UTC
Clean m202 builds without an issue here. The only difference between both builds was the line

ApplyCWS ause074

There. Hmm 8) Ause?

I'll build both and iwll asve the build directories so I can start exchanging modules etc.
Comment 7 pavel 2007-04-05 09:15:47 UTC
So I eliminated all changes from ause074 except solenv changes. The current status is:

m202 builds
m202 with solenv from ause074 SIGSEGVs

I'll now eliminate changes from CWS-ause074-solenv.diff to see what is the problem... Will take some time 
again ;-)
Comment 8 quetschke 2007-04-08 22:56:20 UTC
@Pavel: Sorry, I was on a short Easter vacation and couldn't respond earlier. Yes,
as expected, your cygcheck log looks fine.

Instead of trying to find the problem the hard way, can you try a cygwin snapshot
<http://cygwin.com/snapshots/> (just replace your cygwin1.dll) and see if that
helps?
Comment 9 pavel 2007-04-09 13:53:09 UTC
Well, in the same environment, I can build OOF680_m14 and up to and including SRC680_m202. m203 
brought these problems. I want to track them.

So far, all builds indicate it is tg_config.mk change from ause074 included in m203.
Comment 10 pavel 2007-04-10 15:01:27 UTC
Duplicate of "Argument list too long" issue.


*** This issue has been marked as a duplicate of 74837 ***
Comment 11 ace_dent 2008-05-17 21:45:35 UTC
The Issue you raised has been marked as 'Resolved' and not updated within the
last 1 year+. I am therefore setting this issue to 'Verified' as the first step
towards Closing it. If you feel this is incorrect, please re-open the issue and
add any comments.

Many thanks,
Andrew
 
Cleaning-up and Closing old Issues
~ The Grand Bug Squash, pre v3 ~
http://marketing.openoffice.org/3.0/announcementbeta.html
Comment 12 ace_dent 2008-05-17 23:50:00 UTC
As per previous posting: Verified -> Closed.
A Closed Issue is a Happy Issue (TM).

Regards,
Andrew