On Tue, 09 Oct 2012, Enrico Maria Giordano wrote: Hi,
> > Enrico > > use -m -n -p > Tried: no GPF. GPF does not have to be reapeatable. The most often source of GPF are uninitialized variables so the runtime results are random depending on the contents od allocated memory. And exactly such sitiation is here: ==6257== Conditional jump or move depends on uninitialised value(s) ==6257== at 0x409E13: yyparse (harbour.sly:1978) ==6257== by 0x4140CF: hb_compCompile (harbour.c:6008) ==6257== by 0x4152C4: hb_compMain (harbour.c:344) ==6257== by 0x402B35: main (hbmain.c:34) Above is valgrind output. It does not work on MS-Windows anyhow you use BCC which has tool giving similar functionlaity: CodeGuard. It's not such powerful as valgrind as is limited to code compiled by BCC witg CG switches but it should also catch this situation. I suggest you to rebuild whole Harbour code with CG and then eliminate all problems it begin to report. You should test compiler and tools like hbtest. best regards, Przemek ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ xHarbour-developers mailing list xHarbour-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xharbour-developers
