On Fri, 23 Apr 2010, Pritpal Bedi wrote: Hi,
> 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 ? Because the bugs was not exploited so far. A classic example of long term problems which used to appear when the code is not written to be safe in all possible cases and generate RTE in some abnormal conditions but never GPF. If code is not written in such way then you have to accept that changing a color of some text printed in completely different part of application may cause global crash because it may change the contents of some memory used without valid intialization or type checking in other code. You can thing about non direct inline method calling just like about above color changing which may but does not have cause application crash due to exploiting some hidden so far problems. > Unfortunately not. It is first OLE, second based > entirely on GTWVG which are Windows only applications. Please make some test using GTWVG code from the beginning of march. It may give you some answers. If your code needs MS-Windows than I suggest to try CodeGuard in BCC builds. It can give similar to Valgrind reports though it's not general CPU with OS API emulator but rather compiled code extension. It needs special C compile time switches to enable some additional protection/ statistic code and link with special runtime library. You should recompile Harbour core code with it and then your code. See INSTALL for info about this BCC CodeGuard switches. best regards, Przemek _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
