[gs-devel] Code coverage of ps files.

[Ray Johnston]

Hi Cheri,

The -dINITDEBUG shows some of what is being executed during the 
initialization.

For more detailed information, there is the (extrememly verbose) -ZI
switch that works with the "debug" build. This spews LOTS of PS interpreter
information to stderr while Ghostscript executes.

It can be turned off and on using the Ghostscript extension to the PS
operator set '.setdebug'. Examples are:

    (I) true .setdebug   % turn on interpreter debugging info
    (I) false .setdebug  % turn off interpreter debugging info

Please see doc/Use.htm##Debug_switches for more info.

I hope this helps a bit.

Regards,
Ray
------------------------------------------------------------------------

Cheri Pompeo wrote:
>
> I see the contents of the ps files loaded onto the stacks.
> Is there a place in the gs c code where I can trap when these are 
> executed?
> If nothing else I can write a program that searches the .ps files to 
> say which lines of code are used.
> Thanks again for any help.
> Cheri
>