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 On Jun 11, 2008, at 11:37 AM, [EMAIL PROTECTED] wrote: >> Toninho, >> >> Please UN-comment also line 1058, and post new trace.log. >> > Ron, this is the content of file: > > vmQuit() > After Idle > After Background > After ExitFunctions > After ModuleFunctions > After setkey > After Debugger > After RDD > After i18n > After Stack > After FOREACH > After WITHOBJECT > After Globals > After memvarsClear > After reset Statics > After Return > After CollectAll > After DisableDestructors > After stackRemove > After clsClear > CollectAll after clsClear > After Statics > CollectAll after Statics > After BreakBlock > CollectAll after BreakBlock > After Err > CollectAll after Err > > > > 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 > ------------------------------------------------------------------------- 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
