Ah! Clever.
Something I'm thinking about, is whether Utah modified C Threads much from
Mach3, and how specific they are to Mach 4. If the answer is "not much",
it might be nice to see if other implementations of cthreads (from RTMach,
for example) might be a little bit better to use, or if maybe we should
rewrite them from scratch ourselves.
--
[ Joseph Mallett <jmallett@[newgold.net|xmrg.com|xMach.org]> ]
[ xMach Core Team xMach: Proactively Unbloated Microkernel BSD ]
[ Proud {Free,Net}BSD User; (Obj)C(++) Programmer ] [ http://xMach.org ]
Support my computer addiction buy something from http://www.jmallett.org
On Sun, 6 May 2001 [EMAIL PROTECTED] wrote:
> I did something else right now. I put an infinite loop (while(1);)right at
> the beginning of cthread_init. If the whole thing still boots up to the
> init panic, then we know the problem is somewhere in the linking...
>
> JAN
>
> On Sun, 6 May 2001, Joseph Mallett wrote:
>
> > ick, that's right, those are C library functions... and the thread order
> > is what's causing issues so we can't use libmach stuff...
> >
> > open()/write()/close() ?
> >
> > --
> > [ Joseph Mallett <jmallett@[newgold.net|xmrg.com|xMach.org]> ]
> > [ xMach Core Team xMach: Proactively Unbloated Microkernel BSD ]
> > [ Proud {Free,Net}BSD User; (Obj)C(++) Programmer ] [ http://xMach.org ]
> >
> > Support my computer addiction buy something from http://www.jmallett.org
> >
> > On Sun, 6 May 2001 [EMAIL PROTECTED] wrote:
> >
> > > That does not work for me. I get an error when we try to sandwich the
> > > whole thing together:
> > >
> > > ...
> > > translate_root.o wiring.o -lthreads -lmach_exec -lmach_sa
> > > /cvs/xMach/obj/kernel/lib/libthreads.a(cthreads.o): In function
> > > `cthread_init':
> > > cthreads.o(.text+0x10e): undefined reference to `fopen'
> > > cthreads.o(.text+0x11e): undefined reference to `fprintf'
> > > cthreads.o(.text+0x12a): undefined reference to `fclose'
> > > cthreads.o(.text+0x139): undefined reference to `fprintf'
> > > gmake[3]: *** [bootstrap] Error 1
> > >
> > > How do I add those references?
> > >
> > > JAN
> > > On Sun, 6 May 2001, Joseph Mallett wrote:
> > >
> > > > fprintf(stderr, "Moocow\n"); ?
> > > >
> > > > or output it to a regular file in /, like
> > > > FILE *debugging_file;
> > > > debugging_file = fopen("/xMach-debugging", "a");
> > > > fprintf(debugging_file, "Log message thingo\n");
> > > > fclose(debugging_file);
> > > >
> > > > --
> > > > [ Joseph Mallett <jmallett@[newgold.net|xmrg.com|xMach.org]> ]
> > > > [ xMach Core Team xMach: Proactively Unbloated Microkernel BSD ]
> > > > [ Proud {Free,Net}BSD User; (Obj)C(++) Programmer ] [ http://xMach.org ]
> > > >
> > > > Support my computer addiction buy something from http://www.jmallett.org
> > > >
> > > > On Sun, 6 May 2001 [EMAIL PROTECTED] wrote:
> > > >
> > > > > How can we get around 2.?
> > > > >
> > > > > JAn
> > > > >
> > > > > On Sun, 6 May 2001, Joseph Mallett wrote:
> > > > >
> > > > > > No mind losing. That's a bad thing.
> > > > > >
> > > > > > I'll poke through LiteS makefiles and see if anything is linking in wrong
> > > > > > order.
> > > > > >
> > > > > > I would bet 2. is true, 1. is not, and that 3. is possible.
> > > > > >
> > > > > > --
> > > > > > [ Joseph Mallett <jmallett@[newgold.net|xmrg.com|xMach.org]> ]
> > > > > > [ xMach Core Team xMach: Proactively Unbloated Microkernel BSD ]
> > > > > > [ Proud {Free,Net}BSD User; (Obj)C(++) Programmer ] [ http://xMach.org ]
> > > > > >
> > > > > > Support my computer addiction buy something from http://www.jmallett.org
> > > > > >
> > > > > > On Sun, 6 May 2001 [EMAIL PROTECTED] wrote:
> > > > > >
> > > > > > > I have to admit that I have the harshest problems debugging this thing.
> > > > > > > According to documentation, cthreads are kinda initialized automatically.
> > > > > > > cthread_init() is supposed to be called in _start just as long as its
> > > > > > > linked via -lthread before -lmach. Debug messages in cthread_init are not
> > > > > > > displayed, so I can see three different pssibilities:
> > > > > > > 1. the docs lie and we have to call some sort of initialization.
> > > > > > > 2. the printf statements cannot write to the console and get ignored
> > > > > > > somehow.
> > > > > > > 3. we forgot to put -lthread in a place that matters...
> > > > > > >
> > > > > > > I am loosing my mind.
> > > > > > >
> > > > > > > JAn
> > > > > > >
> > > > > > > On Sun, 6 May 2001, Joseph Mallett wrote:
> > > > > > >
> > > > > > > > The Mach stuff is from Utah, Lites is from Utah's version, as well as
> > > > > > > > NTT's RTMach Lites. User is from Utah's User22.
> > > > > > > >
> > > > > > > > The _layout_ is drastically different, because I wanted to make
>building
> > > > > > > > slightly saner.
> > > > > > > >
> > > > > > > > --
> > > > > > > > [ Joseph Mallett <jmallett@[newgold.net|xmrg.com|xMach.org]>
>]
> > > > > > > > [ xMach Core Team xMach: Proactively Unbloated Microkernel BSD
>]
> > > > > > > > [ Proud {Free,Net}BSD User; (Obj)C(++) Programmer ] [ http://xMach.org
>]
> > > > > > > >
> > > > > > > > Support my computer addiction buy something from
>http://www.jmallett.org
> > > > > > > >
> > > > > > > > On Sun, 6 May 2001 [EMAIL PROTECTED] wrote:
> > > > > > > >
> > > > > > > > > I am wondering where the current code base is coming from. I am just
> > > > > > > > > looking at the code available from UTAH, and the whole thing looks
>very
> > > > > > > > > different. So what parts come from where, please?
> > > > > > > > >
> > > > > > > > > JAn
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
