On Sun, 06 Dec 2009, David Arturo Macias Corona wrote: Hi,
> With Harbour 13140: > [E:\harbour911b\harbour\bin\os2\watcom]hbmk2 speedtst -l -kmo -mt > -gc3 -gtos2 > Harbour 2.0.0beta3 (Rev. 13140) > 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 > [...] > [ total application time: ].....................................0.19 > [ total real time: ]...........................................23.47 So here it's OK. > [E:\harbour911b\harbour\bin\os2\watcom]hbmk2 speedtst -l -kmo -mt > -gc3 -gtstd > Harbour 2.0.0beta3 (Rev. 13140) > 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.06 03:56:34 OS/2 4.50 > Harbour 2.0.0beta3 (Rev. 13140) (MT)+ Open Watcom C++ 12.80.8 (32-bit) x86 > THREADS: all->56 > N_LOOPS: 1000000 > [ T000: empty loop overhead ]...................................0.00 > ====================================================================SYS1808: > The process has stopped. The software diagnostic > code (exception code) is 0001. Fine. Now we confirm that exactly the same problem is in OW CTRL. So let's make > For me we are in same state as in 12-16 November 2008, but with new > Harbour and OpenWatcom and without slow-freeze in MT with "-s" > removed We now much more. > Now we only added selective removing of "-s" in specific places, but > real cause of GPF and solution are un-known yet We only do not know the exact place but this is a job for OpenWatcom developers to fix it. I do not plan to make it myself. Anyhow we can make some other tests to reduce the problem yet and better tune final self contain example which can be used in bug report. > For this reason I suggested to review/recall old messages, and to > contact OpenWatcom developers for deeper research I do not see anything what we can find in the old messages. Now we are moving very fast because you made only small tests without jumping and touching many different things as year ago. It really greatly helps me because I do not have to guess which options interacts with the problem. The fact that I guess correctly and current tests confirmed it is not enough for me. I'll be very happy if you can make yet few tests which may help to find better workaround and create bug report for OW developers. Probably I will need 1 or 2 tests yet - it will depend on their results. First I will want to check if enabling code to check stack overflow at any call level is enough workaround for this problem. For this test I'll remove -s from GTSTD compile time flags in next commit. Then please recompile it and make tests with: hbmk2 speedtst -l -kmo -mt -gc3 -gtstd and: speedtst.exe --thread if it does not help then it will be the last test. If it helps then I'll ask you about yet another one. Then I'll try to write self contain example. That's all. Thank you very much for your help. best regards, Przemek _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
