On Mon, 07 Dec 2009, David Arturo Macias Corona wrote: Hi,
> Harbour 13153 > config\os2\watcom.mk contain: > ifeq ($(filter $(LIBNAME),gtos2 gtstd),) > CFLAGS += -s > endif Have you made clean Harbour build? > [E:\harbour911b\harbour\bin\os2\watcom]hbmk2 speedtst -l -kmo -mt > -gc3 -gtstd > Harbour 2.0.0beta3 (Rev. 13153) > Copyright (c) 1999-2010, http://www.harbour-project.org/ > Compiling 'speedtst.prg'... > Lines 1204, Functions/Procedures 79 > Generating C source output to 'speedtst.c'... Done. > [E:\harbour911b\harbour\bin\os2\watcom]speedtst.exe --thread > 2009.12.07 05:23:28 OS/2 4.50 > Harbour 2.0.0beta3 (Rev. 13153) (MT)+ Open Watcom C++ 12.80.8 (32-bit) x86 > THREADS: all->56 > N_LOOPS: 1000000 > [ T000: empty loop overhead ]...................................0.03 > ====================================================================SYS1808: > The process has stopped. The software diagnostic > code (exception code) is 0001. Thank you very much. It means that the code used to check stack overflow have to be executed exactly by the function which calls APIENTRY16. It also means that recompiling whole Harbour code without -s flag does not resolve the problem of GTSTD because it uses kbhit() from OpenWatcom C RTL compiled without stack debug code. Am I rirght? > With this change gtstd fail with GPF and gtos2 run fine > It is expected so ? Yes but only if you can confirm that after removing CFLAGS += -s from config\os2\watcom.mk and rebuilding whole Harbour code also does not help and GTSTD still GPF. This is the last thing I would like to know. If it's true then I can create self contain example which always GPFs regardless of used compilation flags. Again thank you very much for your time and tests. best regards, Przemek _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
