>> While dropping INLINE is good idea for performance, it's 
>> very wrong idea to fix GPF by changing the code.... I can't 
>> repeat that enough, but seemingly without any reception on 
>> the other end :( I can't reckon why you find it a good 
>> idea to fix GPF by introducing kludges on the .prg level...
>> 
> 
> Tell me why my application running absolutely fine with 
> BCC, MSVC till 15 Mar 2010 stopped on one feature after that.
> Without changing anything in other code ?  How do you attribute 
> as buggy code. Simply changing from INLINE to SETGET method 
> fixed the issue. I am still at a loss what should I look into 
> in such case. I am conversant with CLASSES and its internal.

If you notice such problem, you need to provide an 
example or test it yourself. There is just little 
point in guessing around.

F.e. I had a GPFs in perfectly valid Harbour code 
(HB_RUN(), WAPI_SHELLEXECUTE(), HB_GTI_CLIPBOARD*) 
the other week and instead of bringing it here to 
the list without any pointers (like test code), 
I made my local research and finally fixed it by 
freshly rebuilding all components, which in the 
case of this release I forgot.

I'm not saying this will fix your case, but before 
trying to raise GPFs here, it's good to sort out 
all possibilities locally (I know it's painful).

It's warning sign if you find GPF is plain obvious 
places like INLINE (or HB_RUN()), that the problem 
is likely not in Harbour, otherwise someone would 
have stumbled upon it, especially since March 15.

> Again, I am not trying to prove anything. 
> Just trying to explore what is buggy in my code so that I 
> do fix it in a proper manner.

That's alright.

>> If your code can build on Linux, just run 
>> valgrind on it and post the results. You can find the 
>> exact details in INSTALL about using valgrind.
>> 
> 
> Unfortunately not. It is first OLE, second based 
> entirely on GTWVG which are Windows only applications.
> 
> Leave this discussion, I just showed what I faced and 
> how I resolved.

Przemek pointed to some problem points inside GTWVG 
code. I also touched this code lately to fix remaining 
OLE problems, so you may review/test them.

BTW you can pretty easily sort out GTWVG if you 
restore pre-March 15 version and retest your app.

Brgds,
Viktor

_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to