[M3devel] another Snow Leopard compiler crash
Mika Nystrom
mika at async.caltech.edu
Sat Jan 8 14:47:35 CET 2011
I ran "python upgrade.py" from a clean start (back to head a few weeks ago)
and got:
== package /Users/mika/cm3/cm3/m3-tools/m3bundle ==
+++ /usr/local/cm3/pkg/cm3/I386_DARWIN/cm3 -build -DROOT=/Users/mika/cm3/cm3 +++
--- building in I386_DARWIN ---
ignoring ../src/m3overrides
new source -> compiling m3bundle.m3
-> linking m3bundle
Undefined symbols:
"__alloca", referenced from:
_m3bundle__GetElementSizes in m3bundle.mo
"_Csetjmp__Jumpbuf_size", referenced from:
_Csetjmp__Jumpbuf_size$non_lazy_ptr in m3bundle.mo
(maybe you meant: _Csetjmp__Jumpbuf_size$non_lazy_ptr)
ld: symbol(s) not found
collect2: ld returned 1 exit status
m3_link => 1
linker failed linking: m3bundle
Fatal Error: package build failed
*** execution of [<function _BuildGlobalFunction at 0x10050c5f0>, <function _ShipFunction at 0x10050c668>] failed ***
[hal:cm3/scripts/python] mika%
maybe a conf file change I need to make?
Why only in m3bundle?
Mika
Jay K writes:
>--_6374b72e-0dad-4a03-8d22-4a59e0218226_
>Content-Type: text/plain; charset="iso-8859-1"
>Content-Transfer-Encoding: quoted-printable
>
>I upgrade across incompatibilities frequently & Hudson does now too. The ex=
>isting scripts work very well and you would be foolish to not use them. Jus=
>t use upgrade.py. It is very easy. Or upgrade.py nocleangcc. And then do-cm=
>3-all.py skipgcc realclean && do-cm3-all.py buildship.py.
>
> - Jay/phone
>
>> To: jay.krell at cornell.edu
>> Date: Sat=2C 8 Jan 2011 04:14:41 -0800
>> From: mika at async.caltech.edu
>> CC: m3devel at elegosoft.com
>> Subject: Re: [M3devel] another Snow Leopard compiler crash
>>=20
>> Jay K writes:
>> >
>> >Please try this Mika. It fixes the problem for me.
>>=20
>> Hi Jay=2C
>>=20
>> So I upgraded to the CVS head and now I get a segfaulting compiler:
>>=20
>> [hal:cm3/m3-libs/m3core] mika% gdb $CM3
>> GNU gdb 6.3.50-20050815 (Apple version gdb-1510) (Wed Sep 22 02:45:02 UTC=
> 2010)
>> Copyright 2004 Free Software Foundation=2C Inc.
>> GDB is free software=2C covered by the GNU General Public License=2C and =
>you are
>> welcome to change it and/or distribute copies of it under certain conditi=
>ons.
>> Type "show copying" to see the conditions.
>> There is absolutely no warranty for GDB. Type "show warranty" for detail=
>s.
>> This GDB was configured as "x86_64-apple-darwin"...Reading symbols for sh=
>ared libraries ...... done
>>=20
>> (gdb) run
>> Starting program: /usr/local/cm3/pkg/cm3/I386_DARWIN/cm3=20
>> Reading symbols for shared libraries .+++++.......... done
>>=20
>> Program received signal EXC_BAD_ACCESS=2C Could not access memory.
>> Reason: KERN_PROTECTION_FAILURE at address: 0x0000038b
>> 0x9713354b in _longjmp ()
>> (gdb) where
>> #0 0x9713354b in _longjmp ()
>> #1 0x00285d2b in RTExFrame__InvokeHandler (f=3D0xbffff34c=2C a=3D0xbffff=
>23c) at ../src/runtime/ex_frame/RTExFrame.m3:175
>> #2 0x00285be4 in RTException__ResumeRaise (a=3D0xbffff23c) at ../src/run=
>time/ex_frame/RTExFrame.m3:145
>> #3 0x00285a1b in RTException__Raise (act=3D0xbffff23c) at ../src/runtime=
>/ex_frame/RTExFrame.m3:91
>> #4 0x00269d44 in RTHooks__Raise (ex=3D0x35a720=2C arg=3D0x181cddc=2C mod=
>ule=3D0x398080=2C line=3D50) at ../src/runtime/common/RTHooks.m3:79
>> #5 0x0023adbc in OSErrorPosix__Raise0 (errno=3D2) at ../src/os/POSIX/OSE=
>rrorPosix.m3:50
>> #6 0x0023cffc in FSPosix__Fail (p=3D0x181cdc0=2C f=3D0xf049f0) at ../src=
>/os/POSIX/FSPosix.m3:359
>> #7 0x0023cdd4 in FS__Status (pn=3D0x181cdc0=2C _result=3D0xbffff3c8) at =
>../src/os/POSIX/FSPosix.m3:328
>> #8 0x00217d24 in M3File__IsReadable (path=3D0x181cdc0) at ../src/M3File.=
>m3:123
>> #9 0x000a057f in MxConfig__TryConfig (a=3D0x3255e0=2C b=3D0x3255f0=2C c=
>=3D0x0) at ../src/MxConfig.m3:122
>> #10 0x0009ff67 in MxConfig__FindConfig () at ../src/MxConfig.m3:51
>> #11 0x0009fcd8 in MxConfig__FindFile () at ../src/MxConfig.m3:19
>> #12 0x0002c446 in Main__DoIt () at ../src/Main.m3:32
>> #13 0x0002d1e9 in Main_M3 (mode=3D1) at ../src/Main.m3:214
>> #14 0x0027a781 in RTLinker__RunMainBody (m=3D0x3705a0) at ../src/runtime/=
>common/RTLinker.m3:406
>> #15 0x00279bb6 in RTLinker__AddUnitI (m=3D0x3705a0) at ../src/runtime/com=
>mon/RTLinker.m3:113
>> #16 0x00279c3a in RTLinker__AddUnit (b=3D0x2d1d0) at ../src/runtime/commo=
>n/RTLinker.m3:122
>> #17 0x00002cfc in main (argc=3D1=2C argv=3D0xbffff674=2C envp=3D0xbffff67=
>c) at _m3main.c:16
>> (gdb)=20
>>=20
>> I followed upgrade instructions from Tony (including upgrading the
>> back-end)---I have edited the instructions a bit to track changes in=20
>> CM3. I'm starting from head three weeks old..
>>=20
>> Mika
>>=20
>>=20
>> Return-Path: hosking at cs.purdue.edu
>> Delivery-Date: Sun Jun 24 07:38:38 2007
>> In-Reply-To: <200706231838.l5NIcRef079333 at camembert.async.caltech.edu>
>> References: <200706231838.l5NIcRef079333 at camembert.async.caltech.edu>
>>=20
>> Sounds like we really need some work done in this area. I very =20
>> rarely use the build scripts=2C since I bootstrap manually from old =20
>> compilers to new compilers rather than use the scripts. I suggest =20
>> the following approach=2C which I hope you will try=2C and then report =20
>> back on.
>>=20
>> Install the bootstrap compiler as you did originally:
>>=20
>> > rm -rf /usr/local/cm3/*
>> >
>> > cd ~/cm3-cvs
>> > mkdir boot
>> > cd boot
>> > tar xzvf ../cm3-min-POSIX-FreeBSD4-d5.3.1-2005-10-05.tgz
>> > ./cminstall
>>=20
>>=20
>> Now you will have some kind of cm3 installed=2C presumably in /usr/=20
>> local/cm3/bin/cm3.
>>=20
>> Make sure you have a fresh CVS checkout in directory cm3 (let's =20
>> assume this is in your home directory ~/cm3). Also=2C make sure you =20
>> have an up-to-date version of the CM3 backend compiler cm3cg =20
>> installed by executing the following:
>>=20
>> STEP 0:
>>=20
>> export CM3=3D/usr/local/cm3/bin/cm3
>> cd ~/cm3/m3-sys/m3cc
>> $CM3
>> $CM3 -ship
>>=20
>> You can skip this last step if you know your backend compiler is up =20
>> to date.
>>=20
>> Now=2C let's build the new compiler from scratch (this is the sequence =20
>> I use regularly to test changes to the run-time system whenever I =20
>> make them):
>>=20
>> can replace compilation step with
>>=20
>> rm -rf <der. dir> && $CM3 && $CM3 -ship=20
>>=20
>>=20
>> STEP 1:
>>=20
>> (do these LATER if bootstrapping from old compiler!)
>> cd ~/cm3/m3-libs/m3core
>> $CM3
>> $CM3 -ship
>> cd ~/cm3/m3-libs/libm3
>> $CM3
>> $CM3 -ship
>>=20
>> Now build the compiler:
>>=20
>> cd ~/cm3/m3-libs/sysutils =3B $CM3 etc.
>>=20
>> cd ~/cm3/m3-sys/m3middle=3B $CM3 etc.
>>=20
>> repeat for:
>>=20
>> m3-sys/m3objfile=20
>>=20
>> m3-sys/m3back=20
>>=20
>> m3-sys/m3linker
>>=20
>> m3-sys/m3front
>>=20
>> m3-sys/m3quake
>>=20
>> m3-sys/cm3
>>=20
>> [ here we may need -DROOT=3D<root dir=2C e.g.=2C /home/mika/cm3> ]
>>=20
>>=20
>> At this point you should have a bootstrapped version of cm3 installed =20
>> in the directory /usr/local/cm3/pkg/cm3/TARGET/cm3 (where TARGET is =20
>> the CM3 target platform you are building on -- e.g.=2C LINUXLIBC6=2C =20
>> PPC_DARWIN=2C ...). Note that this did not overwrite your original =20
>> installed compiler in /usr/local/cm3/bin/cm3. We
>> are now going to test the new compiler=2C which was built using the old =
>=20
>> compiler=2C by bootstrapping it one more time.
>>=20
>>=20
>> ******* THIS IS WHERE I HAVE A SEGFAULTING COMPILER *******
>>=20
>> (If m3core and libm3 were skipped earlier=2C do them now=2C and RE-DO all
>> of the above packages before proceeding.)
>>=20
>> From here on out=2C please replace TARGET with your target platform as =20
>> appropriate.
>>=20
>> STEP 2:
>>=20
>> export CM3=3D/usr/local/cm3/pkg/cm3/TARGET/cm3
>> cd ~/cm3/scripts
>>=20
>> ./do-cm3-std.sh realclean
>> REPEAT STEP 1 to rebuild the libraries and the compiler using the =20
>> STEP 1 bootstrap compiler.
>>=20
>> Now you have a STEP 2 bootstrap compiler installed in /usr/local/cm3/=20
>> pkg/cm3/TARGET/cm3. Let's assume the new compiler now works properly =20
>> since it successfully bootstrapped itself=2C but to be sure we can now =20
>> use it to rebuild the world:
>>=20
>> cd ~/cm3/scripts
>> ./do-cm3-std.sh realclean
>> ./do-cm3-std.sh buildship
>>=20
>> Assuming this succeeded then we can be pretty sure /usr/local/cm3/pkg/=20
>> cm3/TARGET/cm3 is good=2C so we can make it our default compiler by =20
>> replacing the original /usr/local/cm3/bin/cm3:
>>=20
>> cp $CM3 /usr/local/cm3/bin/cm3
>>=20
>> On Jun 23=2C 2007=2C at 2:38 PM=2C Mika Nystrom wrote:
>>=20
>> > Ok=2C I'm sorry if I seem a bit dimwitted in the morning like this=2C
>> > but how exactly does one get started? I wish there were a file called
>> > "GETTING_STARTED" or something like that in scripts...
>> >
>> > My Mac is very slow so I switched to my FreeBSD/i386 system (which has
>> > PM3 happily installed on it) and tried to install CM3 from scratch.
>> > Here are the exact commands I typed.
>> >
>> >
>> > rm -rf /usr/local/cm3/*
>> >
>> > cd ~/cm3-cvs
>> > mkdir boot
>> > cd boot
>> > tar xzvf ../cm3-min-POSIX-FreeBSD4-d5.3.1-2005-10-05.tgz
>> > ./cminstall
>> >
>> > # now I seem to have some kind of cm3 installed=2C /usr/local/cm3/bin/=
>=20
>> > cm3
>> >
>> > cd cm3 # location of my CM3 checkout
>> > cvs update -d .
>> >
>> > cd scripts
>> > ./boot-cm3-with-m3.sh realclean
>> > ./do-cm3-std.sh realclean
>> >
>> > ./upgrade.sh # fails here=2C libm3 not compiled
>> > ./boot-cm3-with-m3.sh build # builds cm3=2C but fails on =20
>> > cminstall=2C patternmatching not built
>> >
>> > ./do-cm3-std.sh build # OK
>> > ./do-cm3-std.sh buildship # OK
>> >
>> > ./boot-cm3-with-m3.sh realclean # start over
>> > ./boot-cm3-with-m3.sh build # OK
>> > ./boot-cm3-with-m3.sh buildship # OK
>> >
>> > ./do-cm3-std.sh realclean # OK
>> > ./do-cm3-std.sh build # dies miserably... maybe the =20
>> > compiler can't handle the new libraries?
>> >
>> > ./install-cm3-compiler.sh upgrade # OK=2C new cm3 binary installed
>> >
>> > After all that=2C "game over." I have a cm3 that segfaults.
>> >
>> > Text.i3: In function 'Text_I3':
>> > Text.i3:81: internal compiler error: Segmentation fault
>> > Please submit a full bug report=2C
>> > with preprocessed source if appropriate.
>> > See <URL:http://gcc.gnu.org/bugs.html> for instructions.
>> > compilation failed =3D> not building library "libm3core.a"
>> > Fatal Error: package build failed
>> > *** execution of failed ***
>> >
>> > I can't seem to get either m3gdb or gdb to say anything reasonable
>> > either. ktrace shows nothing out of the ordinary.
>> >
>> > -----
>> >
>> > Meanwhile=2C my Mac got through "do-cm3-std.sh realclean" and
>> > "do-cm3-std.sh buildship" but my compiles are still dying on the
>> > same assertion tickled by ktok. On that machine I have INSTALLROOT
>> > set to ~/cm3=2C but hopefully that has nothing to do with it...
>> >
>> > -----
>> >
>> > Does do-cm3-std.sh realclean clean EVERYTHING? If so my Mac should
>> > really have a fresh setup. The FreeBSD=2C I am not sure=2C maybe the
>> > old binary version just doesn't work right? Of course I could try
>> > bootstrapping with PM3 as well... but really=2C there's an "approved"
>> > process to get from a blank system=2C no?
>> >
>> > Mika
>> >
>> >
>> >
>> >
>> > Tony Hosking writes:
>> >> That sounds like you forgot to execute "do-cm3-std.sh realclean"
>> >> before initiating the build. These sorts of errors sometimes arise
>> >> if there are old build directories lying around.
>> >>
>> >> On Jun 23=2C 2007=2C at 3:34 AM=2C Mika Nystrom wrote:
>> >>
>> >>> Hello everyone=2C
>> >>>
>> >>> I am in the process of trying to consolidate build systems for a
>> >>> few software packages I am maintaining. Currently=2C I am using an
>> >>> old PM3 on FreeBSD4=2C an ancient PM3 (from Klagenfurt?) for Windows
>> >>> (NT386GNU)=2C and trying to get the latest CM3 from cvs up and =20
>> >>> compiling
>> >>> things on PPC_DARWIN. Ideally=2C I'd like to standardize everything
>> >>> on the new PM3---mainly so that I can use pickles (and Network
>> >>> Objects) across all three systems. I'd also like to add Linux to
>> >>> the mix.
>> >>>
>> >>> It's natural for me to start with CM3 on Darwin=2C as there's no
>> >>> alternative. But I am getting some assertions failing. Everything
>> >>> in the CM3 distribution compiles fine=2C and I believe I have compile=
>d
>> >>> the libraries a few times (that is=2C including with themselves)=2C a=
>nd
>> >>> updated the compiler=2C too (using boot-cm3-with-m3.sh). I just cvs
>> >>> updated tonight.
>> >>>
>> >>> Here's what I'm running into:
>> >>>
>> >>> /Users/mika/t/parserlib/ktok/PPC_DARWIN/tok ../src/CHP.t -o =20
>> >>> CHPTok.i3
>> >>>
>> >>> ***
>> >>> *** runtime error:
>> >>> *** <*ASSERT*> failed.
>> >>> *** file "../src/runtime/common/RTCollector.m3"=2C line 2314
>> >>> ***
>> >>>
>> >>> Abort
>> >>>
>> >>> Also:
>> >>>
>> >>> /Users/mika/t/parserlib/ktok/PPC_DARWIN/tok ../src/PRS.t -o =20
>> >>> PRSTok.i3
>> >>> Illegal instruction
>> >>>
>> >>> As you can see=2C these things are coming from the caltech_parser. I
>> >> am using
>> >>> our local version=2C but I don't think it is very different from what
>> >>> is in the
>> >>> CM3 tree.
>> >>>
>> >>> Examining the first error (the failed assertion) more closely=2C I se=
>e
>> >>> the following:
>> >>>
>> >>> (gdb) list
>> >>> 108 wr :=3D FileWr.Open(Pathname.ReplaceExt(tp.out=2C "m3"))=
>=3B
>> >>> 109 EXCEPT OSError.E =3D>
>> >>> 110 Debug.Error("Cannot open tok implementation output
>> >>> file: " &
>> >>> 111 Pathname.ReplaceExt(tp.out=2C "m3"))=3B
>> >>> 112 END=3B
>> >>> 113 Wr.PutText(wr=2C subs.apply(Bundle.Get(Form=2C =20
>> >>> "tokform.m3")))=3B
>> >>> 114 Wr.Close(wr)=3B
>> >>> 115 END Main.
>> >>> (gdb) where
>> >>> #0 0x9004308c in kill ()
>> >>> #1 0x9009fb3c in abort ()
>> >>> #2 0x00096f50 in RTOS__Crash () at RTOS.m3:20
>> >>> #3 0x0005bd40 in RTProcess__Crash (M3_Bd56fi_msg=3D0x0) at
>> >>> RTProcess.m3:65
>> >>> #4 0x0008e4e0 in RTError__EndError (M3_AicXUJ_crash=3D1 '\001') at
>> >>> RTError.m3:115
>> >>> #5 0x0008e08c in RTError__MsgS (M3_AJWxb1_file=3D0xc63d8=2C
>> >>> M3_AcxOUs_line=3D2314=2C M3_Bd56fi_msgA=3D0xca3d0=2C
>> >>> M3_Bd56fi_msgB=3D0xcbe90=2C M3_Bd56fi_msgC=3D0xca3d0) at RTError.m3:4=
>0
>> >>> #6 0x0008eb88 in RTException__Crash (M3_Cblw37_a=3D0xbfffee00=2C
>> >>> M3_AicXUJ_raises=3D0 '\0'=2C M3_AJWxb1_rte=3D0xcb538) at RTException.=
>m3:79
>> >>> #7 0x0008e74c in RTException__DefaultBackstop
>> >>> (M3_Cblw37_a=3D0xbfffee00=2C M3_AicXUJ_raises=3D0 '\0') at =20
>> >>> RTException.m3:39
>> >>> #8 0x0008e614 in RTException__InvokeBackstop
>> >>> (M3_Cblw37_a=3D0xbfffee00=2C M3_AicXUJ_raises=3D0 '\0') at =20
>> >>> RTException.m3:25
>> >>> #9 0x00095d04 in RTException__Raise (M3_Cblw37_act=3D0xbfffee00) at
>> >>> RTExFrame.m3:29
>> >>> #10 0x0008e840 in RTException__DefaultBackstop
>> >>> (M3_Cblw37_a=3D0xbfffee00=2C M3_AicXUJ_raises=3D0 '\0') at =20
>> >>> RTException.m3:47
>> >>> #11 0x0008e614 in RTException__InvokeBackstop
>> >>> (M3_Cblw37_a=3D0xbfffee00=2C M3_AicXUJ_raises=3D0 '\0') at =20
>> >>> RTException.m3:25
>> >>> #12 0x00095d04 in RTException__Raise (M3_Cblw37_act=3D0xbfffee00) at
>> >>> RTExFrame.m3:29
>> >>> #13 0x00079740 in RTHooks__ReportFault (M3_AJWxb1_module=3D0xb3eb8=2C
>> >>> M3_AcxOUs_info=3D74048) at RTHooks.m3:110
>> >>> #14 0x0006ff4c in _m3_fault (M3_AcxOUs_arg=3D74048)
>> >>> #15 0x0006bcf4 in RTHooks__CheckStoreTraced
>> >>> (M3_Af40ku_ref=3D0xb2415c) at RTCollector.m3:2314
>> >>> #16 0x000700e4 in ThreadPThread__InnerLockMutex
>> >>> (M3_AYIbX3_m=3D0xb2415c=2C M3_BXP32l_self=3D0xb24014) at
>> >>> ThreadPThread.m3:126
>> >>> #17 0x000704d8 in ThreadPThread__LockMutex (M3_AYIbX3_m=3D0xb2415c)
>> >>> at ThreadPThread.m3:153
>> >>> #18 0x00019b24 in Wr__PutText (M3_BxxOH1_wr=3D0xb2415c=2C
>> >>> M3_Bd56fi_t=3D0xb44d5c) at Wr.m3:93
>> >>> #19 0x00003f74 in Main_M3 (M3_AcxOUs_mode=3D1) at Main.m3:113
>> >>> #20 0x0005b1c4 in RTLinker__RunMainBody (M3_DjPxE3_m=3D0xad190) at
>> >>> RTLinker.m3:399
>> >>> #21 0x00059f88 in RTLinker__AddUnitI (M3_DjPxE3_m=3D0xad190) at
>> >>> RTLinker.m3:113
>> >>> #22 0x0005a084 in RTLinker__AddUnit (M3_DjPxE5_b=3D0x3600) at
>> >>> RTLinker.m3:122
>> >>> #23 0x00001fac in main (argc=3D4=2C argv=3D0xbffffb24=2C envp=3D0xbff=
>ffb38)
>> >>> at _m3main.mc:4
>> >>> (gdb)
>> >>>
>> >>> The second error:
>> >>>
>> >>> Program received signal EXC_BAD_INSTRUCTION=2C Illegal instruction/
>> >>> operand.
>> >>> 0x00b111ac in ?? ()
>> >>> (gdb) where
>> >>> #0 0x00b111ac in ?? ()
>> >>> #1 0x0001214c in TextSubs__Apply (M3_CN69dV_self=3D0xb26450=2C
>> >>> M3_Bd56fi_src=3D0xb21cec) at TextSubs.m3:63
>> >>> #2 0x0005b1c4 in RTLinker__RunMainBody (M3_DjPxE3_m=3D0xad190) at
>> >>> RTLinker.m3:399
>> >>> #3 0x00059f88 in RTLinker__AddUnitI (M3_DjPxE3_m=3D0xad190) at
>> >>> RTLinker.m3:113
>> >>> #4 0x0005a084 in RTLinker__AddUnit (M3_DjPxE5_b=3D0x3600) at
>> >>> RTLinker.m3:122
>> >>> #5 0x00001fac in main (argc=3D4=2C argv=3D0xbffffb24=2C envp=3D0xbff=
>ffb38)
>> >>> at _m3main.mc:4
>> >>> (gdb) list
>> >>> 58 BEGIN
>> >>> 59 WHILE pos < textLen DO
>> >>> 60 c :=3D Text.GetChar(src=2C pos)=3B
>> >>> 61 IF c IN self.starts THEN
>> >>> 62 (* S("analysing: " & Text.Sub(src=2C pos)=2C
>> >>> DebugLevel)=3B *)
>> >>> 63 iter :=3D self.tbl.iterateOrdered()=3B
>> >>> 64 ind :=3D pos=3B
>> >>> 65 original :=3D ""=3B
>> >>> 66 REPEAT
>> >>> 67 INC(ind)=3B
>> >>> (gdb)
>> >>>
>> >>> Any ideas what to look at?
>> >>>
>> >>> I don't know if this is relevant:
>> >>>
>> >>> [lapdog:~/t/cit_parse/PPC_DARWIN] mika% uname -a
>> >>> Darwin lapdog.local 7.9.0 Darwin Kernel Version 7.9.0: Wed Mar 30
>> >>> 20:11:17 PST 2005=3B root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC Power
>> >>> Macintosh powerpc
>> >>> [lapdog:~/t/cit_parse/PPC_DARWIN] mika% gcc -v
>> >>> Reading specs from /usr/libexec/gcc/darwin/ppc/3.3/specs
>> >>> Thread model: posix
>> >>> gcc version 3.3 20030304 (Apple Computer=2C Inc. build 1666)
>> >>>
>> >>> Mika
>> >>>
>> >>> P.S. Am I correct in assuming that I can get CM3 to build on =20
>> >>> Windows?
>> >>> I could switch to CM3 on Unix any time=2C of course=2C but I've never
>> >>> had luck with it on Windows=2C which is why I am using the ancient
>> >>> Klagenfurt PM3=2C which comes on 40-odd "floppies" and a .EXE that
>> >>> unpacks them into C: (and installation instructions only in German).
>> >>> If CM3 doesn't work on Windows=2C I am essentially wasting my time=2C
>> >>> as the current project I am working on absolutely requires that the
>> >>> software run on Windows 2003 Server (yes=2C it sucks=2C but what can
>> >>> you do?) The very old PM3 at least kind of hobbles along on this
>> >>> platform---actually=2C better than that=3B it does Trestle natively
>> >>> under Windows (no X required)=2C at least on SOME Windows machines.
>> >>>
>> >>> P.P.S. Sorry for all the postscripts=2C but is it true that the
>> >>> build system has been changed so that building with overrides =20
>> >>> (cm3 -x)
>> >>> requires having the compiler sources available? It didn't use to
>> >>> be that way=2C but I can't get Network Objects to work with overrides
>> >>> now unless I have the sources available... It's a bit of a pain
>> >>> because it means that every user has to have the compiler sources=2C
>> >>> or else ship everything=2C or was that not the intention?
> =
>
>--_6374b72e-0dad-4a03-8d22-4a59e0218226_
>Content-Type: text/html; charset="iso-8859-1"
>Content-Transfer-Encoding: quoted-printable
>
><html>
><head>
><style><!--
>.hmmessage P
>{
>margin:0px=3B
>padding:0px
>}
>body.hmmessage
>{
>font-size: 10pt=3B
>font-family:Tahoma
>}
>--></style>
></head>
><body class=3D'hmmessage'>I upgrade across incompatibilities frequently & H=
>udson does now too. The existing scripts work very well and you would be fo=
>olish to not use them. Just use upgrade.py. It is very easy. Or upgrade.py =
>nocleangcc. And then do-cm3-all.py skipgcc realclean && do-cm3-all.py build=
>ship.py.<br><br> - Jay/phone<br><br>> To:=3B jay.krell@=3Bcornell.edu=
><br>> Date:=3B Sat=2C 8 Jan 2011 04:=3B14:=3B41 -0800<br>> From=
>8=3B mika@=3Basync.caltech.edu<br>> CC:=3B m3devel@=3Belegosoft.co=
>m<br>> Subject:=3B Re:=3B [=3BM3devel]=3B another Snow Leopard =
>compiler crash<br>> <br>> Jay K writes:=3B<br>> >=3B<br>> >=3BPlea=
>se try this Mika. It fixes the problem for me.<br>> <br>> Hi Jay=2C<br>> <b=
>r>> So I upgraded to the CVS head and now I get a segfaulting compiler:=
>=3B<br>> <br>> [=3Bhal:=3Bcm3/m3-libs/m3core]=3B mika%=3B gdb &=
>#36=3BCM3<br>> GNU gdb 6.3.50-20050815 (=3BApple version gdb-1510)=3B=
> (=3BWed Sep 22 02:=3B45:=3B02 UTC 2010)=3B<br>> Copyright 2004=
> Free Software Foundation=2C Inc.<br>> GDB is free software=2C covered by t=
>he GNU General Public License=2C and you are<br>> welcome to change it and/=
>or distribute copies of it under certain conditions.<br>> Type "=3Bshow =
>copying"=3B to see the conditions.<br>> There is absolutely no warranty =
>for GDB. Type "=3Bshow warranty"=3B for details.<br>> This GDB was c=
>onfigured as "=3Bx86_64-apple-darwin"=3B...Reading symbols for shared=
> libraries ...... done<br>> <br>> (=3Bgdb)=3B run<br>> Starting progr=
>am:=3B /usr/local/cm3/pkg/cm3/I386_DARWIN/cm3 <br>> Reading symbols for =
>shared libraries .+=3B+=3B+=3B+=3B+=3B.......... done<br>> <=
>br>> Program received signal EXC_BAD_ACCESS=2C Could not access memory.<br>=
>> Reason:=3B KERN_PROTECTION_FAILURE at address:=3B 0x0000038b<br>> 0=
>x9713354b in _longjmp (=3B)=3B<br>> (=3Bgdb)=3B where<br>> #=
>=3B0 0x9713354b in _longjmp (=3B)=3B<br>> #=3B1 0x00285d2b in RT=
>ExFrame__InvokeHandler (=3Bf==3B0xbffff34c=2C a==3B0xbffff23c)=
>=3B at ../src/runtime/ex_frame/RTExFrame.m3:=3B175<br>> #=3B2 0x0028=
>5be4 in RTException__ResumeRaise (=3Ba==3B0xbffff23c)=3B at ../src=
>/runtime/ex_frame/RTExFrame.m3:=3B145<br>> #=3B3 0x00285a1b in RTExc=
>eption__Raise (=3Bact==3B0xbffff23c)=3B at ../src/runtime/ex_frame=
>/RTExFrame.m3:=3B91<br>> #=3B4 0x00269d44 in RTHooks__Raise (=3Be=
>x==3B0x35a720=2C arg==3B0x181cddc=2C module==3B0x398080=2C line=
>1=3B50)=3B at ../src/runtime/common/RTHooks.m3:=3B79<br>> #=3B5 0=
>x0023adbc in OSErrorPosix__Raise0 (=3Berrno==3B2)=3B at ../src/os/=
>POSIX/OSErrorPosix.m3:=3B50<br>> #=3B6 0x0023cffc in FSPosix__Fail &=
>#40=3Bp==3B0x181cdc0=2C f==3B0xf049f0)=3B at ../src/os/POSIX/FSPos=
>ix.m3:=3B359<br>> #=3B7 0x0023cdd4 in FS__Status (=3Bpn==3B0x1=
>81cdc0=2C _result==3B0xbffff3c8)=3B at ../src/os/POSIX/FSPosix.m3:=
>=3B328<br>> #=3B8 0x00217d24 in M3File__IsReadable (=3Bpath==3B0x=
>181cdc0)=3B at ../src/M3File.m3:=3B123<br>> #=3B9 0x000a057f in M=
>xConfig__TryConfig (=3Ba==3B0x3255e0=2C b==3B0x3255f0=2C c==3B0=
>x0)=3B at ../src/MxConfig.m3:=3B122<br>> #=3B10 0x0009ff67 in MxCo=
>nfig__FindConfig (=3B)=3B at ../src/MxConfig.m3:=3B51<br>> #=3B=
>11 0x0009fcd8 in MxConfig__FindFile (=3B)=3B at ../src/MxConfig.m3=
>8=3B19<br>> #=3B12 0x0002c446 in Main__DoIt (=3B)=3B at ../src/Mai=
>n.m3:=3B32<br>> #=3B13 0x0002d1e9 in Main_M3 (=3Bmode==3B1)=
>=3B at ../src/Main.m3:=3B214<br>> #=3B14 0x0027a781 in RTLinker__RunM=
>ainBody (=3Bm==3B0x3705a0)=3B at ../src/runtime/common/RTLinker.m3=
>:=3B406<br>> #=3B15 0x00279bb6 in RTLinker__AddUnitI (=3Bm==3B0=
>x3705a0)=3B at ../src/runtime/common/RTLinker.m3:=3B113<br>> #=3B1=
>6 0x00279c3a in RTLinker__AddUnit (=3Bb==3B0x2d1d0)=3B at ../src/r=
>untime/common/RTLinker.m3:=3B122<br>> #=3B17 0x00002cfc in main (=
>=3Bargc==3B1=2C argv==3B0xbffff674=2C envp==3B0xbffff67c)=3B at=
> _m3main.c:=3B16<br>> (=3Bgdb)=3B <br>> <br>> I followed upgrade i=
>nstructions from Tony (=3Bincluding upgrading the<br>> back-end)=3B--=
>-I have edited the instructions a bit to track changes in <br>> CM3. I'=
>=3Bm starting from head three weeks old..<br>> <br>> Mika<br>> <br>> =
><br>> Return-Path:=3B hosking@=3Bcs.purdue.edu<br>> Delivery-Date:=
>=3B Sun Jun 24 07:=3B38:=3B38 2007<br>> In-Reply-To:=3B <=3B200=
>706231838.l5NIcRef079333@=3Bcamembert.async.caltech.edu>=3B<br>> Refe=
>rences:=3B <=3B200706231838.l5NIcRef079333@=3Bcamembert.async.calt=
>ech.edu>=3B<br>> <br>> Sounds like we really need some work done in this=
> area. I very <br>> rarely use the build scripts=2C since I bootstrap man=
>ually from old <br>> compilers to new compilers rather than use the script=
>s. I suggest <br>> the following approach=2C which I hope you will try=2C=
> and then report <br>> back on.<br>> <br>> Install the bootstrap compiler =
>as you did originally:=3B<br>> <br>> >=3B rm -rf /usr/local/cm3/*=
>=3B<br>> >=3B<br>> >=3B cd ~=3B/cm3-cvs<br>> >=3B mkdir boot<b=
>r>> >=3B cd boot<br>> >=3B tar xzvf ../cm3-min-POSIX-FreeBSD4-d5.3.1-=
>2005-10-05.tgz<br>> >=3B ./cminstall<br>> <br>> <br>> Now you will have =
>some kind of cm3 installed=2C presumably in /usr/ <br>> local/cm3/bin/cm3.<=
>br>> <br>> Make sure you have a fresh CVS checkout in directory cm3 (=3B=
>let'=3Bs <br>> assume this is in your home directory ~=3B/cm3)=
>=3B. Also=2C make sure you <br>> have an up-to-date version of the CM3 ba=
>ckend compiler cm3cg <br>> installed by executing the following:=3B<br>=
>> <br>> STEP 0:=3B<br>> <br>> export CM3==3B/usr/local/cm3/bin/cm3<br=
>>> cd ~=3B/cm3/m3-sys/m3cc<br>> $=3BCM3<br>> $=3BCM3 -ship<br>> <=
>br>> You can skip this last step if you know your backend compiler is up <=
>br>> to date.<br>> <br>> Now=2C let'=3Bs build the new compiler from scr=
>atch (=3Bthis is the sequence <br>> I use regularly to test changes to =
>the run-time system whenever I <br>> make them)=3B:=3B<br>> <br>> ca=
>n replace compilation step with<br>> <br>> rm -rf <=3Bder. dir>=3B &#=
>38=3B&=3B $=3BCM3 &=3B&=3B $=3BCM3 -ship <br>> <br>> <br>> S=
>TEP 1:=3B<br>> <br>> (=3Bdo these LATER if bootstrapping from old com=
>piler!=3B)=3B<br>> cd ~=3B/cm3/m3-libs/m3core<br>> $=3BCM3<br>=
>> $=3BCM3 -ship<br>> cd ~=3B/cm3/m3-libs/libm3<br>> $=3BCM3<br>> =
>$=3BCM3 -ship<br>> <br>> Now build the compiler:=3B<br>> <br>> cd &#=
>126=3B/cm3/m3-libs/sysutils ;=3B $=3BCM3 etc.<br>> <br>> cd ~=3B/=
>cm3/m3-sys/m3middle;=3B $=3BCM3 etc.<br>> <br>> repeat for:=3B<br>=
>> <br>> m3-sys/m3objfile <br>> <br>> m3-sys/m3back <br>> <br>> m3-sys/m3lin=
>ker<br>> <br>> m3-sys/m3front<br>> <br>> m3-sys/m3quake<br>> <br>> m3-sys/c=
>m3<br>> <br>> [=3B here we may need -DROOT==3B<=3Broot dir=2C e.g.=
>=2C /home/mika/cm3>=3B ]=3B<br>> <br>> <br>> At this point you should=
> have a bootstrapped version of cm3 installed <br>> in the directory /usr/=
>local/cm3/pkg/cm3/TARGET/cm3 (=3Bwhere TARGET is <br>> the CM3 target p=
>latform you are building on -- e.g.=2C LINUXLIBC6=2C <br>> PPC_DARWIN=2C .=
>..)=3B. Note that this did not overwrite your original <br>> installed=
> compiler in /usr/local/cm3/bin/cm3. We<br>> are now going to test the new=
> compiler=2C which was built using the old <br>> compiler=2C by bootstrapp=
>ing it one more time.<br>> <br>> <br>> *=3B*=3B*=3B*=3B*=3B&=
>#42=3B*=3B THIS IS WHERE I HAVE A SEGFAULTING COMPILER *=3B*=3B=
>2=3B*=3B*=3B*=3B*=3B<br>> <br>> (=3BIf m3core and libm3 were=
> skipped earlier=2C do them now=2C and RE-DO all<br>> of the above packages=
> before proceeding.)=3B<br>> <br>> From here on out=2C please replace TA=
>RGET with your target platform as <br>> appropriate.<br>> <br>> STEP 2:=
>=3B<br>> <br>> export CM3==3B/usr/local/cm3/pkg/cm3/TARGET/cm3<br>> cd &=
>#126=3B/cm3/scripts<br>> <br>> ./do-cm3-std.sh realclean<br>> REPEAT STEP 1=
> to rebuild the libraries and the compiler using the <br>> STEP 1 bootstra=
>p compiler.<br>> <br>> Now you have a STEP 2 bootstrap compiler installed i=
>n /usr/local/cm3/ <br>> pkg/cm3/TARGET/cm3. Let'=3Bs assume the new com=
>piler now works properly <br>> since it successfully bootstrapped itself=
>=2C but to be sure we can now <br>> use it to rebuild the world:=3B<br>=
>> <br>> cd ~=3B/cm3/scripts<br>> ./do-cm3-std.sh realclean<br>> ./do-cm=
>3-std.sh buildship<br>> <br>> Assuming this succeeded then we can be pretty=
> sure /usr/local/cm3/pkg/ <br>> cm3/TARGET/cm3 is good=2C so we can make it=
> our default compiler by <br>> replacing the original /usr/local/cm3/bin/c=
>m3:=3B<br>> <br>> cp $=3BCM3 /usr/local/cm3/bin/cm3<br>> <br>> On Jun=
> 23=2C 2007=2C at 2:=3B38 PM=2C Mika Nystrom wrote:=3B<br>> <br>> =
>2=3B Ok=2C I'=3Bm sorry if I seem a bit dimwitted in the morning like th=
>is=2C<br>> >=3B but how exactly does one get started?=3B I wish ther=
>e were a file called<br>> >=3B "=3BGETTING_STARTED"=3B or somethin=
>g like that in scripts...<br>> >=3B<br>> >=3B My Mac is very slow so =
>I switched to my FreeBSD/i386 system (=3Bwhich has<br>> >=3B PM3 happ=
>ily installed on it)=3B and tried to install CM3 from scratch.<br>> >=
>=3B Here are the exact commands I typed.<br>> >=3B<br>> >=3B<br>> =
>2=3B rm -rf /usr/local/cm3/*=3B<br>> >=3B<br>> >=3B cd ~=3B/cm=
>3-cvs<br>> >=3B mkdir boot<br>> >=3B cd boot<br>> >=3B tar xzvf ..=
>/cm3-min-POSIX-FreeBSD4-d5.3.1-2005-10-05.tgz<br>> >=3B ./cminstall<br>>=
> >=3B<br>> >=3B #=3B now I seem to have some kind of cm3 installed=
>=2C /usr/local/cm3/bin/ <br>> >=3B cm3<br>> >=3B<br>> >=3B cd cm3 =
> #=3B location of my CM3 checkout<br>> >=3B cvs update -d .<br>> =
>2=3B<br>> >=3B cd scripts<br>> >=3B ./boot-cm3-with-m3.sh realclean<b=
>r>> >=3B ./do-cm3-std.sh realclean<br>> >=3B<br>> >=3B ./upgrade.s=
>h #=3B fails here=2C libm3 not compiled<br>> >=
>=3B ./boot-cm3-with-m3.sh build #=3B builds cm3=2C but fails on <=
>br>> >=3B cminstall=2C patternmatching not built<br>> >=3B<br>> >=
>=3B ./do-cm3-std.sh build #=3B OK<br>> >=3B ./do-cm3-std.=
>sh buildship #=3B OK<br>> >=3B<br>> >=3B ./boot-cm3-with-m=
>3.sh realclean #=3B start over<br>> >=3B ./boot-cm3-with-m3.sh buil=
>d #=3B OK<br>> >=3B ./boot-cm3-with-m3.sh buildship #=3B O=
>K<br>> >=3B<br>> >=3B ./do-cm3-std.sh realclean #=3B OK<br=
>>> >=3B ./do-cm3-std.sh build #=3B dies miserably... mayb=
>e the <br>> >=3B compiler can'=3Bt handle the new libraries?=3B<b=
>r>> >=3B<br>> >=3B ./install-cm3-compiler.sh upgrade #=3B OK=2C ne=
>w cm3 binary installed<br>> >=3B<br>> >=3B After all that=2C "=3Bg=
>ame over."=3B I have a cm3 that segfaults.<br>> >=3B<br>> >=3B Te=
>xt.i3:=3B In function '=3BText_I3'=3B:=3B<br>> >=3B Text.i3&=
>#58=3B81:=3B internal compiler error:=3B Segmentation fault<br>> >=
>=3B Please submit a full bug report=2C<br>> >=3B with preprocessed sourc=
>e if appropriate.<br>> >=3B See <=3BURL:=3Bhttp:=3B//gcc.gnu.or=
>g/bugs.html>=3B for instructions.<br>> >=3B compilation failed ==
>=3B>=3B not building library "=3Blibm3core.a"=3B<br>> >=3B Fata=
>l Error:=3B package build failed<br>> >=3B *=3B*=3B*=3B exe=
>cution of failed *=3B*=3B*=3B<br>> >=3B<br>> >=3B I can'=
>=3Bt seem to get either m3gdb or gdb to say anything reasonable<br>> >=
>=3B either. ktrace shows nothing out of the ordinary.<br>> >=3B<br>> &#=
>62=3B -----<br>> >=3B<br>> >=3B Meanwhile=2C my Mac got through "=
>=3Bdo-cm3-std.sh realclean"=3B and<br>> >=3B "=3Bdo-cm3-std.sh bui=
>ldship"=3B but my compiles are still dying on the<br>> >=3B same asse=
>rtion tickled by ktok. On that machine I have INSTALLROOT<br>> >=3B set=
> to ~=3B/cm3=2C but hopefully that has nothing to do with it...<br>> &#=
>62=3B<br>> >=3B -----<br>> >=3B<br>> >=3B Does do-cm3-std.sh realc=
>lean clean EVERYTHING?=3B If so my Mac should<br>> >=3B really have =
>a fresh setup. The FreeBSD=2C I am not sure=2C maybe the<br>> >=3B old =
>binary version just doesn'=3Bt work right?=3B Of course I could try<=
>br>> >=3B bootstrapping with PM3 as well... but really=2C there'=3Bs =
>an "=3Bapproved"=3B<br>> >=3B process to get from a blank system=
>=2C no?=3B<br>> >=3B<br>> >=3B Mika<br>> >=3B<br>> >=
>=3B<br>> >=3B<br>> >=3B<br>> >=3B Tony Hosking writes:=3B<br>> =
>>=3B>=3B That sounds like you forgot to execute "=3Bdo-cm3-std.sh =
>realclean"=3B<br>> >=3B>=3B before initiating the build. These so=
>rts of errors sometimes arise<br>> >=3B>=3B if there are old build di=
>rectories lying around.<br>> >=3B>=3B<br>> >=3B>=3B On Jun 23=
>=2C 2007=2C at 3:=3B34 AM=2C Mika Nystrom wrote:=3B<br>> >=3B>=
>=3B<br>> >=3B>=3B>=3B Hello everyone=2C<br>> >=3B>=3B>=3B=
><br>> >=3B>=3B>=3B I am in the process of trying to consolidate bu=
>ild systems for a<br>> >=3B>=3B>=3B few software packages I am mai=
>ntaining. Currently=2C I am using an<br>> >=3B>=3B>=3B old PM3 on=
> FreeBSD4=2C an ancient PM3 (=3Bfrom Klagenfurt?=3B)=3B for Window=
>s<br>> >=3B>=3B>=3B (=3BNT386GNU)=3B=2C and trying to get th=
>e latest CM3 from cvs up and <br>> >=3B>=3B>=3B compiling<br>> &#=
>62=3B>=3B>=3B things on PPC_DARWIN. Ideally=2C I'=3Bd like to sta=
>ndardize everything<br>> >=3B>=3B>=3B on the new PM3---mainly so t=
>hat I can use pickles (=3Band Network<br>> >=3B>=3B>=3B Objects=
>)=3B across all three systems. I'=3Bd also like to add Linux to<br>>=
> >=3B>=3B>=3B the mix.<br>> >=3B>=3B>=3B<br>> >=3B>=
>=3B>=3B It'=3Bs natural for me to start with CM3 on Darwin=2C as ther=
>e'=3Bs no<br>> >=3B>=3B>=3B alternative. But I am getting some=
> assertions failing. Everything<br>> >=3B>=3B>=3B in the CM3 dist=
>ribution compiles fine=2C and I believe I have compiled<br>> >=3B>=3B=
>>=3B the libraries a few times (=3Bthat is=2C including with themselv=
>es)=3B=2C and<br>> >=3B>=3B>=3B updated the compiler=2C too =
>0=3Busing boot-cm3-with-m3.sh)=3B. I just cvs<br>> >=3B>=3B>=
>=3B updated tonight.<br>> >=3B>=3B>=3B<br>> >=3B>=3B>=3B =
>Here'=3Bs what I'=3Bm running into:=3B<br>> >=3B>=3B>=3B<=
>br>> >=3B>=3B>=3B /Users/mika/t/parserlib/ktok/PPC_DARWIN/tok ../s=
>rc/CHP.t -o <br>> >=3B>=3B>=3B CHPTok.i3<br>> >=3B>=3B>=
>=3B<br>> >=3B>=3B>=3B *=3B*=3B*=3B<br>> >=3B>=3B=
>2=3B *=3B*=3B*=3B runtime error:=3B<br>> >=3B>=3B>=3B =
>*=3B*=3B*=3B <=3B*=3BASSERT*=3B>=3B failed.<br>> &#=
>62=3B>=3B>=3B *=3B*=3B*=3B file "=3B../src/runtime/com=
>mon/RTCollector.m3"=3B=2C line 2314<br>> >=3B>=3B>=3B *=3B&#=
>42=3B*=3B<br>> >=3B>=3B>=3B<br>> >=3B>=3B>=3B Abort<br=
>>> >=3B>=3B>=3B<br>> >=3B>=3B>=3B Also:=3B<br>> >=
>=3B>=3B>=3B<br>> >=3B>=3B>=3B /Users/mika/t/parserlib/ktok/P=
>PC_DARWIN/tok ../src/PRS.t -o <br>> >=3B>=3B>=3B PRSTok.i3<br>> &=
>#62=3B>=3B>=3B Illegal instruction<br>> >=3B>=3B>=3B<br>> &#=
>62=3B>=3B>=3B As you can see=2C these things are coming from the calt=
>ech_parser. I<br>> >=3B>=3B am using<br>> >=3B>=3B>=3B our =
>local version=2C but I don'=3Bt think it is very different from what<br>=
>> >=3B>=3B>=3B is in the<br>> >=3B>=3B>=3B CM3 tree.<br>>=
> >=3B>=3B>=3B<br>> >=3B>=3B>=3B Examining the first error=
> (=3Bthe failed assertion)=3B more closely=2C I see<br>> >=3B>=
>=3B>=3B the following:=3B<br>> >=3B>=3B>=3B<br>> >=3B>=
>=3B>=3B (=3Bgdb)=3B list<br>> >=3B>=3B>=3B 108 wr=
> :=3B==3B FileWr.Open(=3BPathname.ReplaceExt(=3Btp.out=2C "=
>=3Bm3"=3B)=3B)=3B;=3B<br>> >=3B>=3B>=3B 109 EXCE=
>PT OSError.E ==3B>=3B<br>> >=3B>=3B>=3B 110 Debug.Er=
>ror(=3B"=3BCannot open tok implementation output<br>> >=3B>=3B&=
>#62=3B file:=3B "=3B &=3B<br>> >=3B>=3B>=3B 111 =
> Pathname.ReplaceExt(=3Btp.out=2C "=3Bm3"=3B)=3B)=3B;=3B<=
>br>> >=3B>=3B>=3B 112 END;=3B<br>> >=3B>=3B>=3B =
>113 Wr.PutText(=3Bwr=2C subs.apply(=3BBundle.Get(=3BForm=2C =
> <br>> >=3B>=3B>=3B "=3Btokform.m3"=3B)=3B)=3B)=3B&=
>#59=3B<br>> >=3B>=3B>=3B 114 Wr.Close(=3Bwr)=3B;=3B=
><br>> >=3B>=3B>=3B 115 END Main.<br>> >=3B>=3B>=3B &#=
>40=3Bgdb)=3B where<br>> >=3B>=3B>=3B #=3B0 0x9004308c in ki=
>ll (=3B)=3B<br>> >=3B>=3B>=3B #=3B1 0x9009fb3c in abort =
>(=3B)=3B<br>> >=3B>=3B>=3B #=3B2 0x00096f50 in RTOS__Cra=
>sh (=3B)=3B at RTOS.m3:=3B20<br>> >=3B>=3B>=3B #=3B3 =
>0x0005bd40 in RTProcess__Crash (=3BM3_Bd56fi_msg==3B0x0)=3B at<br>=
>> >=3B>=3B>=3B RTProcess.m3:=3B65<br>> >=3B>=3B>=3B &#=
>35=3B4 0x0008e4e0 in RTError__EndError (=3BM3_AicXUJ_crash==3B1 '=
>=3B\=3B001'=3B)=3B at<br>> >=3B>=3B>=3B RTError.m3:=3B=
>115<br>> >=3B>=3B>=3B #=3B5 0x0008e08c in RTError__MsgS (=
>=3BM3_AJWxb1_file==3B0xc63d8=2C<br>> >=3B>=3B>=3B M3_AcxOUs_lin=
>e==3B2314=2C M3_Bd56fi_msgA==3B0xca3d0=2C<br>> >=3B>=3B>=3B =
>M3_Bd56fi_msgB==3B0xcbe90=2C M3_Bd56fi_msgC==3B0xca3d0)=3B at RTEr=
>ror.m3:=3B40<br>> >=3B>=3B>=3B #=3B6 0x0008eb88 in RTExcept=
>ion__Crash (=3BM3_Cblw37_a==3B0xbfffee00=2C<br>> >=3B>=3B>=
>=3B M3_AicXUJ_raises==3B0 '=3B\=3B0'=3B=2C M3_AJWxb1_rte==3B=
>0xcb538)=3B at RTException.m3:=3B79<br>> >=3B>=3B>=3B #=
>=3B7 0x0008e74c in RTException__DefaultBackstop<br>> >=3B>=3B>=3B=
> (=3BM3_Cblw37_a==3B0xbfffee00=2C M3_AicXUJ_raises==3B0 '=3B	=
>2=3B0'=3B)=3B at <br>> >=3B>=3B>=3B RTException.m3:=3B39=
><br>> >=3B>=3B>=3B #=3B8 0x0008e614 in RTException__InvokeBack=
>stop<br>> >=3B>=3B>=3B (=3BM3_Cblw37_a==3B0xbfffee00=2C M3_A=
>icXUJ_raises==3B0 '=3B\=3B0'=3B)=3B at <br>> >=3B>=3B=
>>=3B RTException.m3:=3B25<br>> >=3B>=3B>=3B #=3B9 0x0009=
>5d04 in RTException__Raise (=3BM3_Cblw37_act==3B0xbfffee00)=3B at<=
>br>> >=3B>=3B>=3B RTExFrame.m3:=3B29<br>> >=3B>=3B>=3B=
> #=3B10 0x0008e840 in RTException__DefaultBackstop<br>> >=3B>=3B&#=
>62=3B (=3BM3_Cblw37_a==3B0xbfffee00=2C M3_AicXUJ_raises==3B0 '=
>=3B\=3B0'=3B)=3B at <br>> >=3B>=3B>=3B RTException.m3=
>8=3B47<br>> >=3B>=3B>=3B #=3B11 0x0008e614 in RTException__Invo=
>keBackstop<br>> >=3B>=3B>=3B (=3BM3_Cblw37_a==3B0xbfffee00=
>=2C M3_AicXUJ_raises==3B0 '=3B\=3B0'=3B)=3B at <br>> >=
>=3B>=3B>=3B RTException.m3:=3B25<br>> >=3B>=3B>=3B #=
>=3B12 0x00095d04 in RTException__Raise (=3BM3_Cblw37_act==3B0xbfffee0=
>0)=3B at<br>> >=3B>=3B>=3B RTExFrame.m3:=3B29<br>> >=3B&#=
>62=3B>=3B #=3B13 0x00079740 in RTHooks__ReportFault (=3BM3_AJWxb1_=
>module==3B0xb3eb8=2C<br>> >=3B>=3B>=3B M3_AcxOUs_info==3B740=
>48)=3B at RTHooks.m3:=3B110<br>> >=3B>=3B>=3B #=3B14 0x00=
>06ff4c in _m3_fault (=3BM3_AcxOUs_arg==3B74048)=3B<br>> >=3B=
>2=3B>=3B #=3B15 0x0006bcf4 in RTHooks__CheckStoreTraced<br>> >=3B&=
>#62=3B>=3B (=3BM3_Af40ku_ref==3B0xb2415c)=3B at RTCollector.m3&=
>#58=3B2314<br>> >=3B>=3B>=3B #=3B16 0x000700e4 in ThreadPThread=
>__InnerLockMutex<br>> >=3B>=3B>=3B (=3BM3_AYIbX3_m==3B0xb241=
>5c=2C M3_BXP32l_self==3B0xb24014)=3B at<br>> >=3B>=3B>=3B Th=
>readPThread.m3:=3B126<br>> >=3B>=3B>=3B #=3B17 0x000704d8 in=
> ThreadPThread__LockMutex (=3BM3_AYIbX3_m==3B0xb2415c)=3B<br>> =
>2=3B>=3B>=3B at ThreadPThread.m3:=3B153<br>> >=3B>=3B>=3B=
> #=3B18 0x00019b24 in Wr__PutText (=3BM3_BxxOH1_wr==3B0xb2415c=2C<=
>br>> >=3B>=3B>=3B M3_Bd56fi_t==3B0xb44d5c)=3B at Wr.m3:=
>=3B93<br>> >=3B>=3B>=3B #=3B19 0x00003f74 in Main_M3 (=3BM3_=
>AcxOUs_mode==3B1)=3B at Main.m3:=3B113<br>> >=3B>=3B>=3B =
>#=3B20 0x0005b1c4 in RTLinker__RunMainBody (=3BM3_DjPxE3_m==3B0xad=
>190)=3B at<br>> >=3B>=3B>=3B RTLinker.m3:=3B399<br>> >=3B=
>>=3B>=3B #=3B21 0x00059f88 in RTLinker__AddUnitI (=3BM3_DjPxE3_=
>m==3B0xad190)=3B at<br>> >=3B>=3B>=3B RTLinker.m3:=3B113<=
>br>> >=3B>=3B>=3B #=3B22 0x0005a084 in RTLinker__AddUnit (=
>=3BM3_DjPxE5_b==3B0x3600)=3B at<br>> >=3B>=3B>=3B RTLinker.m=
>3:=3B122<br>> >=3B>=3B>=3B #=3B23 0x00001fac in main (=3B=
>argc==3B4=2C argv==3B0xbffffb24=2C envp==3B0xbffffb38)=3B<br>> =
>>=3B>=3B>=3B at _m3main.mc:=3B4<br>> >=3B>=3B>=3B (=
>=3Bgdb)=3B<br>> >=3B>=3B>=3B<br>> >=3B>=3B>=3B The sec=
>ond error:=3B<br>> >=3B>=3B>=3B<br>> >=3B>=3B>=3B Prog=
>ram received signal EXC_BAD_INSTRUCTION=2C Illegal instruction/<br>> >=
>=3B>=3B>=3B operand.<br>> >=3B>=3B>=3B 0x00b111ac in ?=3B=
>?=3B (=3B)=3B<br>> >=3B>=3B>=3B (=3Bgdb)=3B where<b=
>r>> >=3B>=3B>=3B #=3B0 0x00b111ac in ?=3B?=3B (=3B=
>1=3B<br>> >=3B>=3B>=3B #=3B1 0x0001214c in TextSubs__Apply =
>0=3BM3_CN69dV_self==3B0xb26450=2C<br>> >=3B>=3B>=3B M3_Bd56fi_s=
>rc==3B0xb21cec)=3B at TextSubs.m3:=3B63<br>> >=3B>=3B>=3B=
> #=3B2 0x0005b1c4 in RTLinker__RunMainBody (=3BM3_DjPxE3_m==3B0xa=
>d190)=3B at<br>> >=3B>=3B>=3B RTLinker.m3:=3B399<br>> >=
>=3B>=3B>=3B #=3B3 0x00059f88 in RTLinker__AddUnitI (=3BM3_DjPx=
>E3_m==3B0xad190)=3B at<br>> >=3B>=3B>=3B RTLinker.m3:=3B1=
>13<br>> >=3B>=3B>=3B #=3B4 0x0005a084 in RTLinker__AddUnit =
>0=3BM3_DjPxE5_b==3B0x3600)=3B at<br>> >=3B>=3B>=3B RTLinker.=
>m3:=3B122<br>> >=3B>=3B>=3B #=3B5 0x00001fac in main (=
>=3Bargc==3B4=2C argv==3B0xbffffb24=2C envp==3B0xbffffb38)=3B<br=
>>> >=3B>=3B>=3B at _m3main.mc:=3B4<br>> >=3B>=3B>=3B &=
>#40=3Bgdb)=3B list<br>> >=3B>=3B>=3B 58 BEGIN<br>> >=
>=3B>=3B>=3B 59 WHILE pos <=3B textLen DO<br>> >=3B>=
>=3B>=3B 60 c :=3B==3B Text.GetChar(=3Bsrc=2C pos)=
>=3B;=3B<br>> >=3B>=3B>=3B 61 IF c IN self.starts THE=
>N<br>> >=3B>=3B>=3B 62 (=3B*=3B S(=3B"=3B=
>analysing:=3B "=3B &=3B Text.Sub(=3Bsrc=2C pos)=3B=2C<br>> &=
>#62=3B>=3B>=3B DebugLevel)=3B;=3B *=3B)=3B<br>> >=3B&#=
>62=3B>=3B 63 iter :=3B==3B self.tbl.iterateOrdered=
>0=3B)=3B;=3B<br>> >=3B>=3B>=3B 64 ind :=3B&#=
>61=3B pos;=3B<br>> >=3B>=3B>=3B 65 original :=
>=3B==3B "=3B"=3B;=3B<br>> >=3B>=3B>=3B 66 =
> REPEAT<br>> >=3B>=3B>=3B 67 INC(=3Bind)=3B&#=
>59=3B<br>> >=3B>=3B>=3B (=3Bgdb)=3B<br>> >=3B>=3B>=
>=3B<br>> >=3B>=3B>=3B Any ideas what to look at?=3B<br>> >=
>=3B>=3B>=3B<br>> >=3B>=3B>=3B I don'=3Bt know if this is =
>relevant:=3B<br>> >=3B>=3B>=3B<br>> >=3B>=3B>=3B [=
>=3Blapdog:=3B~=3B/t/cit_parse/PPC_DARWIN]=3B mika%=3B uname -a=
><br>> >=3B>=3B>=3B Darwin lapdog.local 7.9.0 Darwin Kernel Version=
> 7.9.0:=3B Wed Mar 30<br>> >=3B>=3B>=3B 20:=3B11:=3B17 PS=
>T 2005;=3B root:=3Bxnu/xnu-517.12.7.obj~=3B1/RELEASE_PPC Power<b=
>r>> >=3B>=3B>=3B Macintosh powerpc<br>> >=3B>=3B>=3B [=
>=3Blapdog:=3B~=3B/t/cit_parse/PPC_DARWIN]=3B mika%=3B gcc -v<b=
>r>> >=3B>=3B>=3B Reading specs from /usr/libexec/gcc/darwin/ppc/3.=
>3/specs<br>> >=3B>=3B>=3B Thread model:=3B posix<br>> >=3B&#=
>62=3B>=3B gcc version 3.3 20030304 (=3BApple Computer=2C Inc. build 1=
>666)=3B<br>> >=3B>=3B>=3B<br>> >=3B>=3B>=3B Mika<=
>br>> >=3B>=3B>=3B<br>> >=3B>=3B>=3B P.S. Am I correct in =
>assuming that I can get CM3 to build on <br>> >=3B>=3B>=3B Window=
>s?=3B<br>> >=3B>=3B>=3B I could switch to CM3 on Unix any time=
>=2C of course=2C but I'=3Bve never<br>> >=3B>=3B>=3B had luck w=
>ith it on Windows=2C which is why I am using the ancient<br>> >=3B>=
>=3B>=3B Klagenfurt PM3=2C which comes on 40-odd "=3Bfloppies"=3B a=
>nd a .EXE that<br>> >=3B>=3B>=3B unpacks them into C:=3B (=
>=3Band installation instructions only in German)=3B.<br>> >=3B>=3B=
>>=3B If CM3 doesn'=3Bt work on Windows=2C I am essentially wasting my=
> time=2C<br>> >=3B>=3B>=3B as the current project I am working on =
>absolutely requires that the<br>> >=3B>=3B>=3B software run on Win=
>dows 2003 Server (=3Byes=2C it sucks=2C but what can<br>> >=3B>=3B=
>>=3B you do?=3B)=3B The very old PM3 at least kind of hobbles alo=
>ng on this<br>> >=3B>=3B>=3B platform---actually=2C better than th=
>at;=3B it does Trestle natively<br>> >=3B>=3B>=3B under Windows=
> (=3Bno X required)=3B=2C at least on SOME Windows machines.<br>> =
>2=3B>=3B>=3B<br>> >=3B>=3B>=3B P.P.S. Sorry for all the post=
>scripts=2C but is it true that the<br>> >=3B>=3B>=3B build system =
>has been changed so that building with overrides <br>> >=3B>=3B>=
>=3B (=3Bcm3 -x)=3B<br>> >=3B>=3B>=3B requires having the com=
>piler sources available?=3B It didn'=3Bt use to<br>> >=3B>=3B&=
>#62=3B be that way=2C but I can'=3Bt get Network Objects to work with ov=
>errides<br>> >=3B>=3B>=3B now unless I have the sources available.=
>.. It'=3Bs a bit of a pain<br>> >=3B>=3B>=3B because it means =
>that every user has to have the compiler sources=2C<br>> >=3B>=3B>=
>=3B or else ship everything=2C or was that not the intention?=3B<br>
> =
> </body>
></html>=
>
>--_6374b72e-0dad-4a03-8d22-4a59e0218226_--
More information about the M3devel
mailing list