Hi Randy,
Since some week there is one common filename used.
You can control this filename using Set( _SET_HBOUTLOG, <cFileName> ).
You can also add custom information (one line) to all the
log entries generated by Harbour using Set( _SET_HBOUTLOGINFO,
<cFileName ).
Brgds,
Viktor
On 2008.07.03., at 15:09, Randy Portnoff wrote:
Hi Viktor,
Are the only error logs created by Harbour HB_EX.LOG and HB_OUT.LOG
or are there others?
IMO, I think only one filename should be used for _all_ logs and new
errors should be appended to the existing log if it exists.
Regards,
Randy.
At 02:45 PM 7/2/2008, you wrote:
Hi Randy,
Here is the internal error logging implemented.
Copy the file to source/rtl/ and recompile.
Brgds,
Viktor
On 2008.07.02., at 17:21, Randy Portnoff wrote:
Hi all,
Similar to the way Harbour now traps GPF's (and logs some info in a
text file), can it also detect race conditions and log that as
well? I am referring to situations where recursion occurs repeatedly
which causes the app to just exit (ie. vanish). Ideally, a runtime
error would be best.
For example, this causes the app to vanish.
func main()
SomeFunc()
return nil
func SomeFunc()
Main()
return nil
Regards,
Randy.
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
