From: "Dan Sugalski" <[EMAIL PROTECTED]>
So, could someone with some windows experience go digging and find out how one would:
1) Find the address of the base of a thread's stack 3) Find out what a thread's current stack pointer is
I would do 1), 3) this way ...
[Some snippage]
Cool, thanks. I'm not sure exactly what we're going to do at the moment, but I'm glad we can do it. Being able to temporarily pause a thread'll be handy--that's something the POSIX thread interface won't let you do and, while I see the point, it's really handy.
> 2) Find out how big a thread's stack is
By default, OS reserves 1 MB of memory for a thread's stack. One can specify a different size with a linker option or a STACKSIZE statement in the .DEF file. So it's, sort of, up to us how big a thread stack is. No problem here.
Yow. Unless there's a good reason for it to be that big, I think I'd like to go with a smaller stack by default, something more like 20-30K. (Though if there are OS functions that can chew up great gobs of stack space we can certainly go larger)
I appreciate the info, and it'll help get the generic interface for threads nailed down.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
