viewpoint-particle

Author Topic: What is typical delay before DebugTrace info written to disk?  (Read 45 times)

gibberish

  • Newbie
  • *
  • Posts: 20
What is typical delay before DebugTrace info written to disk?
« on: January 03, 2019, 02:31:23 pm »
Background:
My script designed to loop forever.
DebugTrace turned on before entering "endless" (while 1... endwhile) loop.
Script accepts user input.

Problem:
Just interacted with script and opened the debug log file, but do not see the thing I just did. Closed/re-opened, still do not see my action.

1. Is there a delay before debugTrace log info is written to disk?

2. If so, is there a way to "flush" the debug log (i.e. force it to write to disk at a certain point)?

Many thanks!

PS - my guess is that there is zero delay before writing to disk (that DebugTrace() writes to disk after each statement), and that my debug log problem is a problem with my code. But wanted to verify this fact, first.

td

  • Tech Support
  • *****
  • Posts: 2689
    • WinBatch
Re: What is typical delay before DebugTrace info written to disk?
« Reply #1 on: January 04, 2019, 08:06:31 am »
DebugTrace not only writes each line to the trace file on disk but also opens and closes the file for each executed line. Also note that by default DebugTrace does not continue line by line debugging into UDFs, UDSs, or called scripts.  Check out the DebugTrace page in the Consolidated WIL Help file for more information on using the function.
"Success is a lousy teacher. It seduces smart people into thinking they can't lose."
  - Bill Gates