Welcome to NeoOffice developer notes and announcements
NeoOffice
Developer notes and announcements
 
 

This website is an archive and is no longer active
NeoOffice announcements have moved to the NeoOffice News website


Support
· Forums
· NeoOffice Support
· NeoWiki


Announcements
· Twitter @NeoOffice


Downloads
· Download NeoOffice


  
NeoOffice :: View topic - typesconfig crashed during NeoOffice 2.0 build with gcc 4.0.
typesconfig crashed during NeoOffice 2.0 build with gcc 4.0.
 
   NeoOffice Forum Index -> NeoOffice Development
View previous topic :: View next topic  
Author Message
jjmckenzie51
The Anomaly


Joined: Apr 01, 2005
Posts: 1055
Location: Southeastern Arizona

PostPosted: Fri Dec 30, 2005 7:17 pm    Post subject: typesconfig crashed during NeoOffice 2.0 build with gcc 4.0.

Patrick/Mox:

Have you noticed that typesconfig is crashing when doing a NeoOffice 2.0 build with gcc 4.0.1?

Code:

Log segment from CrashReporter:

Host Name:      james-mckenzies-powerbook-g4-15
Date/Time:      2005-12-30 13:28:02.740 -0700
OS Version:     10.4.3 (Build 8F46)
Report Version: 3

Command: typesconfig
Path:    ../unxmacxp.pro/bin/typesconfig
Parent:  typesconfig [3949]

Version: ??? (???)

PID:    3953
Thread: 0

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000000

Thread 0 Crashed:
0   typesconfig    0x00002f0c GetAtAddress + 80 (crt.c:355)
1   typesconfig    0x00002ea0 check + 92 (crt.c:355)
2   typesconfig    0x000030c8 CheckGetAccess + 48 (crt.c:355)
3   typesconfig    0x00003368 InfoMemoryAccess + 40 (crt.c:355)
4   typesconfig    0x00003648 main + 404 (crt.c:355)
5   typesconfig    0x000025dc _start + 340 (crt.c:272)
6   typesconfig    0x00002484 start + 60

Thread 0 crashed with PPC Thread State 64:
  srr0: 0x0000000000002f0c srr1: 0x000000000000d030                        vrsave: 0x0000000000000000
    cr: 0x42000448          xer: 0x0000000000000004   lr: 0x0000000000002ec8  ctr: 0x0000000000002f0c
    r0: 0x0000000000000000   r1: 0x00000000bfffb2a0   r2: 0x0000000000002ef8   r3: 0x0000000000000000
    r4: 0x0000000000000000   r5: 0x00000000fefefeff   r6: 0x0000000080808080   r7: 0x0000000000000000
    r8: 0x0000000000000000   r9: 0x0000000000002f0c  r10: 0x000000008fe07838  r11: 0x0000000000000080
   r12: 0x0000000000002ebc  r13: 0x0000000000000000  r14: 0x0000000000000000  r15: 0x0000000000000000
   r16: 0x0000000000000000  r17: 0x0000000000000000  r18: 0x0000000000000000  r19: 0x0000000000000000
   r20: 0x0000000000000000  r21: 0x0000000000000000  r22: 0x0000000000000000  r23: 0x00000000bfffb530
   r24: 0x0000000000003ce8  r25: 0x0000000000003cf0  r26: 0x0000000000003cf4  r27: 0x0000000000003f24
   r28: 0x0000000000002ebc  r29: 0x0000000000000000  r30: 0x0000000000000000  r31: 0x0000000000002ec8

Binary Images Description:
    0x1000 -     0x3fff typesconfig    /Users/jamesmckenzie/NeoOfficeJ/NeoOffice2.0_test/neojava/build/sal/unxmacxp.pro/bin/typesconfig
  0x405000 -   0x48bfff libstlport_gcc.dylib    /Users/jamesmckenzie/NeoOfficeJ/NeoOffice2.0_test/neojava/build/solver/680/unxmacxp.pro/lib/libstlport_gcc.dylib
0x8fe00000 - 0x8fe54fff dyld 44.2   /usr/lib/dyld
0x90000000 - 0x901b3fff libSystem.B.dylib    /usr/lib/libSystem.B.dylib
0x9020b000 - 0x9020ffff libmathCommon.A.dylib    /usr/lib/system/libmathCommon.A.dylib
0x913ac000 - 0x913b4fff libgcc_s.1.dylib    /usr/lib/libgcc_s.1.dylib
0x913b9000 - 0x913d9fff libmx.A.dylib    /usr/lib/libmx.A.dylib
0x954ac000 - 0x9552ffff libstdc++.6.dylib    /usr/lib/libstdc++.6.dylib



Any idea what is happening? Should this be reported to OpenOffice's IssueZilla?

Thank you.

James
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11949

PostPosted: Fri Dec 30, 2005 8:14 pm    Post subject:

Hmmm. My gcc 4.0.1 build is still running but there are several crashes in my ~/Library/Logs/CrashReporter folder. Also, I looked on my Panther partition and there were several crashes on Panther with gcc 3.3 the last time I built OOo 2.0.

Patrick
Back to top
jjmckenzie51
The Anomaly


Joined: Apr 01, 2005
Posts: 1055
Location: Southeastern Arizona

PostPosted: Fri Dec 30, 2005 8:37 pm    Post subject:

pluby wrote:
Hmmm. My gcc 4.0.1 build is still running but there are several crashes in my ~/Library/Logs/CrashReporter folder. Also, I looked on my Panther partition and there were several crashes on Panther with gcc 3.3 the last time I built OOo 2.0.


This was just the last one, there were several others. I cleared all of the crashreporter logs but this program. Again, should we report this back to OpenOffice? I can try a build of Pavel's build area and see if this program fails after the build of NeoOffice 2.0 pre-alpha completes. I'm at the officecfg part where the .xcu files are build for all SEVENTY-FOUR supported languages. This takes a long time....

James
Back to top
Mox
Operator


Joined: Jun 29, 2005
Posts: 44

PostPosted: Sat Dec 31, 2005 4:02 am    Post subject: languages

jjmckenzie51 wrote:
pluby wrote:
Hmmm. My gcc 4.0.1 build is still running but there are several crashes in my ~/Library/Logs/CrashReporter folder. Also, I looked on my Panther partition and there were several crashes on Panther with gcc 3.3 the last time I built OOo 2.0.


This was just the last one, there were several others. I cleared all of the crashreporter logs but this program. Again, should we report this back to OpenOffice? I can try a build of Pavel's build area and see if this program fails after the build of NeoOffice 2.0 pre-alpha completes. I'm at the officecfg part where the .xcu files are build for all SEVENTY-FOUR supported languages. This takes a long time....

James


To speed up the building process, you might want to add OO_LANGUAGES="en-US" to the make -command. You have to rerun configure, though (rm neojava/build.configure)


Last edited by Mox on Sat Dec 31, 2005 6:29 am; edited 1 time in total
Back to top
jjmckenzie51
The Anomaly


Joined: Apr 01, 2005
Posts: 1055
Location: Southeastern Arizona

PostPosted: Sat Dec 31, 2005 4:15 am    Post subject: Re: languages

Mox wrote:

To speed up the building process, you might want to add OO_LANGUAGES="en-US" to the make -command.


I know that I can do this. However, I want to look for any problem during the OpenOffice build process and this includes building as designed. Yes, it will take longer, but it will also find problems that may not appear if you build only for English-US (and there were some that were found by Pavel and others working on OpenOffice.)

I don't mind the build taking this long as I can use my system for other purposes and I do builds when I'm sleeping or doing other things. I just wanted to let Patrick know that the build was working on 74 languages and that OpenOffice had grown since the 1.1.x days.

James
Back to top
Display posts from previous:   
   NeoOffice Forum Index -> NeoOffice Development All times are GMT - 7 Hours
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum

Powered by phpBB © 2001, 2005 phpBB Group

All logos and trademarks in this site are property of their respective owner. The comments are property of their posters, all the rest © Planamesa Inc.
NeoOffice is a registered trademark of Planamesa Inc. and may not be used without permission.
PHP-Nuke Copyright © 2005 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.