Stack overflow problem ?
BL> Yes, as far as I know EVERY OS has a guard page. […] BL> Be aware that if you have a stack frame which is larger than a BL> page (typically 8k), it is POSSIBLE to jump right over the guard BL> page and not see a SEGV right away. KK> The solution to that is to initialize your locals before calling KK> lower-level functions. […] This is an inadequate solution for the simple reason that one isn’t guaranteed that variables with automatic storage duration are in any particular order on the stack. The initialisations themselves could cause out of order references to areas beyond the guard page, depending from how the compiler chooses to order the storage for the variables. The correct solution is to use a compiler that generates code to perform stack probes in function prologues. For example: All of the commercial C/C++ compilers for 32-bit OS/2 except for Borland’s (i.e. Watcom’s, IBM’s, and MetaWare’s) generate code that does stack probes, since 32-bit OS/2 uses guard pages and a c
