Perforce Public Knowledge Base - Diagnose P4V Problems
Reset Search
 

 

Article

Diagnose P4V Problems

« Go Back

Information

 
Problem

How do I enable command tracing for P4V?

How do I diagnose problems in P4V?
Solution

To enable command tracing, do the following:

  1. Launch P4V.
  2. Choose the following menu and dialog options:
    Edit -> Preferences... -> Logging
  3. Select the following two log options:
    • Show P4 reporting commands (dirs, filelog, fstat, and so on)
    • Show p4 command output for file operations
  4. Select the "Enable logging to file" option if you want the trace output saved in a file. 
  5. Click OK or Apply.
Once P4V commands are displayed, reproduce any problems and right-click "Clear log" to show any errors.

If P4V problems still persist, remove all P4V settings by renaming the .p4qt directory.  You can find the .p4qt directory in Locating Preferences Files for P4V.  Although you will lose all preferences and settings, many P4V problems can be fixed when existing cached data is removed.

Notes:

Detailed logging of P4V operations (command tracing) is available starting with the 2008.2 version of P4V. For versions prior to 2007.1, logging can be enabled via Tools -> Preferences... -> General.

The default P4V log file size is 500K. The log file behaves like a first in, first out (FIFO) buffer. When the log file is full, older information at the front of the log is dropped as new commands are written to the log.

The command tracing feature can slow down P4V, particularly if logging operations to a large file.

Related Links

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255