4 Replies Latest reply: May 21, 2012 11:25 PM by nikantonelli RSS

Documentation for missing commands for coverity_config.xml

Currently Being Moderated

I know there are commands for coverity_config.xml that are not documented in the command reference document such as <extern_trans> and <extern_trans_arg>.


Can I found documentation for these anywhere? We have a trick in our config file involving calling the Perl interpreter and I can't quit understand how this works. Plus I would like to know if there are even more undocumented commands like these.

  • Re: Documentation for missing commands for coverity_config.xml
    Jon Jarboe Moderator
    Currently Being Moderated

    I recommend that you contact Coverity support to get a specific answer to this question.  There are certainly undocumented options in the config files, and they might be able to help you understand what they do.  Keep in mind that there are reasons to leave some options undocumented.  We don't want to encourage folks to shoot themselves in the foot


    As far as the extern_trans, That is a way to convert the compiler command line into something that the Coverity compiler understands.  Typically, it just converts command-line arguments recognized by your compiler into arguments that the Coverity compiler recognizes.  The extern_trans option uses a separate program or script to do this conversion, as opposed to some of the other options (e.g. <replace_arg>) which don't require a separate program.

    • Re: Documentation for missing commands for coverity_config.xml
      kblock Contributor
      Currently Being Moderated

      See Coverity® 6.0.1 Static Analysis Compiler Integration Guide:



      Invokes an external command. The syntax is:



      <extern_trans_path>path to your executable</extern_trans_path>





      The path to the executable is required, but the arguments are optional and will depend on how the

      executable works. In addition to whatever arguments you specify, the following additional arguments

      will be added:


      • The filename containing all the command line arguments that need to be processed, one argument

      per line.

      • The filename of where you should write the new command line, one argument per line.

      • After the first two arguments, there are the following optional arguments that are useful to locate

      helpful files, such as the compile switch table:

      • --cov-home XXX

      • --cov-type YYY

      • --template_subdir ZZZ


      The native command line arguments are not put on the command line to avoid any command line

      length issues and some instability in pipes on Windows.



      Just out of curiosity. What are you using this feature for?

More Like This

  • Retrieving data ...


  • Correct Answers - 10 points
  • Helpful Answers - 5 points