Hello Peter!

Replying to a message of Peter Fitzsimmons to Erik Huelsmann:

 EH>> the thread to open an Object window, using 
 EH>> WinInitialize, I get a Guardpage exception. (I tried

 PF> Complain to the compiler vendor.
I will!

[deleted stuff about stack-expansion using guard-pages]
 PF> That is because thread 1 of all OS/2 programs does not use guard page
 PF> expansion,  contrary to popular belief.  Thread 1 is always wholly
 PF> committed.

This explains some of it!

 EH>> I could write an exception-handler that uses the 
 EH>> guardpage-system to expand the stack, but the 
 EH>> operating system is supposed to be able to do that 
 EH>> itself...

 PF> And it does,  if you have not installed a broken exception handler
 PF> --which sounds like it may be the case for sp/2.
Well, as far as I was able to determine anything from the pascal->ASM
translation (they don't explain the internals of the library :-(  ) they DO
install an exception-handler for thread 1, but I didn't install one for
thread 2 (and neither did the compiler, because I used the api directly
using DosCreateThread). A case of broken exception-handling is not very
likely then (as it seems to me).

I still don't install an exception-handler, but I will just commit the
stack as in thread 1. This is a solution for now, as I will only use the
program for myself for now. Later I might write an
exception-handling-object that I can add to my thread-handling-object. When
I decide to ship the program.

But for now I don't seem to be able to startup a message-queue within the
second thread. Does this have to do with not installing an
exception-handler, or the stack not being of a minimal size?


Bye, Erik!
[TeamOS/2 NL]
preferred personal reactions through e-mail
[internet: ErikH{at}hcc-gron.idn.nl]

--- FleetStreet 1.14 NR