Generating a trace file without timing information
If you want to generate an activity log with no timing information
in a text file, you can turn on PBDebug tracing in the System Options
dialog box. The PBDebug trace file contains a log showing which object
functions and instructions and system DLL functions were executed in
chronological order.
To generate a simple trace file:
-
Select Tools>System Options and check the Enable PBDebug
Tracing check box. -
Check the Prompt Before OverWriting PBDebug Output File box if
you want to retain existing trace output when you run or debug the
application. -
(Optional) Specify a pathname for the PBDebug output
file. -
Run your application.
If you do not check the Prompt Before OverWriting PBDebug
Output File box, PowerBuilder overwrites the existing trace file
every time you run the application or click the Start button in the
debugger. If you check the box, it displays a response window. You
can choose to overwrite the file, append new trace output to the
existing file, or cancel the run or debug session.If you want to retain the trace file, save it with a different
name before running the application, or specify a new file name in
the System Options dialog box.If you do not specify an output file path, PowerBuilder
creates an output file in the same directory as the PowerBuilder
executable file. The output file has the same name as the
PowerBuilder executable with the extension DBG. If you do not have
write permission to this directory, you must specify a value for the
output file path.Turning PBDebug off
Running your application with PBDebug on will slow down
execution. Be sure to clear the Enable PBDebug Tracing check box
on the System Options dialog box if you do not need this trace
information.For information on creating the same kind of diagnostic trace
file when you run your compiled application outside PowerBuilder,
see Tracing execution.