🚀 go-pugleaf

In article <6883@cbmvax.UUCP> thomas@cbmvax.UUCP (Dave Thomas QA) writes:
>You should probably avoid making most compiler library calls (unless you
>have source and can check to see what they are doing).  They often use
>global variables which will cause problems if multiple tasks use the
>library.


Ok, I'll look at that ... I'm using a few Manx lib calls.  Can't 
remember which, though, of hand.

  
>> Anybody have any pointers about where I can start looking?  
>
>"Pointers" is exactly right :-)
>I haven't done Manx in a while, but I think that you are having 
>addressability problems.  If you use any global variables or use any
>compiler provided link library routines, you may need to put a call
>to geta4() in the front of your routines.  You should also disable
>any stack checking code.

I'm using Edwin Hoogerbeets MKLIB as a basis and it provides it's own
geta4() and uses it each time.  It also has it's own .begin label
and one other label that overrides one in c.lib ( I can't remember
which one )

I will check this out.  I hope no important routines are unusable ...
that would be such a pain!
:-)


Thanks,

	Blair
-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-///-=
= Blair MacIntyre, bmacintyre@watcgl.{waterloo.edu, UWaterloo.ca}     \\\///  =
=   now appearing at the Computer Graphics Lab, U of Waterloo!         \XX/   =
= "Don't be mean ... remember, no matter where you go, there you are." BBanzai=