Re: Langwar crash
ChrisBurch2 wrote:
>
> Robert Craig wrote:
> >
> > Chris Burch wrote:
> > > Eu 3.0.1 (and 3.0.0)
> > > SuSE Linux 10.0 64 bit
> > >
> > > Langwar is crashing
> > >
> > > first part of ex.err
> > >
> > > File: ex.err Col 0 16300 bytes
> > >
> > > 0%
> > > ./sched.e:62 in function next_task()
> > > type_check failure, mintime is -11285555.93
> > > mintime = -11285555.93
> > > mintask = 5
> > > i = 5
> > >
> > > ... called from lw.ex:261 in procedure trek()
> > > nk = <no value>
> > >
> > > ... called from lw.ex:321
> >
> > mintime is declared as a positive_atom.
> > I don't think I ever guarantee in the docs that time()
> > will return a non-negative number, though it
> > seems to do that in all cases I've seen. I only
> > talk about measuring *differences* in time() from one call to
> > the next. Maybe you can add
> > without type_check
> > to the top of lw.exu and see what happens.
> > You might also try a small test to see if time() advances at the
> > correct rate.
> >
> > Regards,
> > Rob Craig
> > Rapid Deployment Software
> > <a href="http://www.RapidEuphoria.com">http://www.RapidEuphoria.com</a>
>
>
> Hi
>
> How curious, my time() returns a -ve integer (and it does advance at the
> correct rate)
>
> From the docs
>
> Description: Return the number of seconds since some fixed point in the past.
>
> Does this mean that I am writing this, on this computer, before this fixed
> point in the past?
>
> Simply add this above procedure sched() in sched.e
>
> global function my_time()
> return time() + 12000000
> end function
>
> and replace all instances of time() with my_time throughout the whole of
> langwar,
>
> to bring yourself 'up to date', or 'back to the future', or..... etc
>
> Chris
Hi
Is this a feature of time() on 64 bit systems? Is this a dignostic technique for
telling you are running on a 64 bit system? Should it be fixed? Does it matter?
What will happen in 2036?
Chris
|
Not Categorized, Please Help
|
|