[M3devel] help booting CM3 on FreeBSD 4.11?

Jay jay.krell at cornell.edu
Sat Apr 25 06:12:54 CEST 2009


Cool.

 

 > If I use user threads, it's a different story (which is probably too bad,


Oops, right, I forgot, I should have mentioned that, user threads have likely been broken on all platforms for a while. I noticed that on PPC_LINUX. I think it is trivial to fix. Or use pthreads..

 

 

 - Jay

 
> To: jay.krell at cornell.edu
> Date: Fri, 24 Apr 2009 20:38:17 -0700
> From: mika at async.caltech.edu
> CC: m3devel at elegosoft.com
> Subject: Re: [M3devel] help booting CM3 on FreeBSD 4.11?
> 
> Jay (and others),
> 
> Success! I think.... I was able to build the compiler, after much
> experimentation, by using Jay's build order and linking with -libc_r.
> Mentor works, and that's usually a good sign.
> 
> Jay, your assembly worked too! And as you say, it's much easier to
> bootstrap with that than to do what I was trying to do (but I did
> both, several times, just to make sure).
> 
> I don't know why I was having linking problems with -libc_r earlier.
> Now it just seems to work. So, pthreads on FreeBSD 4.
> 
> If I use user threads, it's a different story (which is probably too bad,
> as I know that user threads work absolutely fine in my old version of CM3):
> 
> I can build a compiler fine, but the bootstrapped cm3 crashes in
> the user thread code. Note that exactly the same thing happens whether
> I bootstrap with the assembly version from Jay or from v. 5.3.4, which
> I think is what I had. Here we go:
> 
> Starting program: /usr/local/cm3/pkg/cm3/FreeBSD4/cm3 
> 
> Program received signal SIGSEGV, Segmentation fault.
> 16_82568bb in RTHooks.PushEFrame (frame=16_bfbff3f4) at ../src/thread/POSIX/ThreadPosix.m3:1599
> 1599 f.next := self.context.handlers;
> (gdb) where
> #0 16_82568bb in RTHooks.PushEFrame (frame=16_bfbff3f4) at ../src/thread/POSIX/ThreadPosix.m3:1599

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20090425/7cf7f632/attachment-0002.html>


More information about the M3devel mailing list