🚀 go-pugleaf

In article <1992Nov20.224547.66@rei.com> fox@rei.com (Fuzzy Fox) writes:
 >vincent@datmuc.UUCP (vincent) writes:
 vincent@datmuc.dat.de
 
 >	data. tsrstack = malloc (1024);
 >	data. tsrstack += 1024;				// go to the top of it

 >Are you sure that malloc'd memory stays part of your program?  It seems
 >to me that when your program terminates, all heap memory will be free'd
 >by the OS and the next program that loads in (such as COMMAND.COM) will
 >load into the place where your stack used to be.  You should probably
 >use a static stack.

I tried to no avail. I also tried the current stack. Well I'm not shure
If the switching stack code is correct.

I just got mail (twice) about turning off the interrupts inside the timer
function, or before switching stack. I assumed that durring an interrupt
the interrupt were automaticly disabled, but I haven't verified, let me
get on my perriscope and find out. I'll get back to you guys.

An now back to news. (This guys going to DOS)

vincent@datmuc.dat.de

ciao!