Toninho, Why not? The customer is not likely to see serious difference.
Here's what you need to do: 1. Set EnvVar as per my previous reply. 2. MAKE_B32 CLEAN 3. Build your app with that debug build of xHarbour, using same compile and link flags as per above, and make sure to link cg32.lib as FIRST library. The resulting EXE will be slightly bigger, and little slower, but otherwise it should work the same, and should not bother your customer. Then after GPF, forward the YourAppName.cgl file, it should have all info we need to quickly resolve the problem. Ron On Jun 11, 2008, at 4:34 PM, [EMAIL PROTECTED] wrote: >> Toninho, >> >> With full C debug build it's easy to know exactly the problem, as you >> get the exact call trace for the offensive line. Please see my reply >> to Luis. > > Ron, I'll try but is very hard to get this GPF, and I can't send a > full C debug EXE to my client... > > Regards, > > Toninho. > > > ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ xHarbour-developers mailing list xHarbour-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xharbour-developers
