On Tue, 08 Dec 2009, David Arturo Macias Corona wrote: Hi,
> I expected not to fail in gtos2 and gtstd, but as gtstd failed, I > checked files and made confirmations to be sure, and at last I added > "config\os2\watcom.mk" content in message for clarity Thank you very much. > >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? > Why you ask to me, are you trying to confuse me ? :-) No, I do not want to confuse you :-) Just simply I was asking about results of whole Harbour build without -s flag to close the tests. > As I see you are closing the circle Exactly but I wanted to be sure. > I repeated tests with fresh SVN: Harbour 13162 > and some changes > As summary: > - gtstd fail (GPF) with and without > CFLAGS += -s > - gtos2 run > with CFLAGS += -s : fast ? > without CFLAGS += -s : slow > Sequence are below, and segments of make_ow.log confirm switchs used in > Harbour build [...] > *** Clean, build using in config\os2\watcom.mk: > # CFLAGS += -s > [E:\harbour912\harbour\bin\os2\watcom]hbmk2 speedtst -l -kmo -mt -gc3 -gtstd > Harbour 2.0.0beta3 (Rev. 13162) > 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:\harbour912\harbour\bin\os2\watcom]speedtst.exe --thread > 2009.12.07 22:59:37 OS/2 4.50 > Harbour 2.0.0beta3 (Rev. 13162) (MT)+ Open Watcom C++ 12.80.8 (32-bit) x86 > THREADS: all->56 > N_LOOPS: 1000000 > [ T000: empty loop overhead ]...................................0.10 > ====================================================================SYS1808: > The process has stopped. The software diagnostic > code (exception code) is 0001. And this is the confirmation I was asking for. Thank you very much for you help and all tests. Now I can write self contain example which illustrates the problem. I want to create two ones. The first one will allways fail exploiting the problem inside OW CRTL and the scond one will fail only when compiled with -s showing where exactly the problem is. I'll try to make it in this week and then I would like to ask you to make final tests with them to check if they really GPFs. I hope that For someone who well know Open Watcom internals such code examples allows to locate and fix the problem quite fast so in next OW releases it will work correctly. best regards, Przemek _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
