vppreproc --debug option does not enable debug messages for VCS-like parameters
|Assignee:||Wilson Snyder||% Done:|
The code for this command contains a number of debug print statements intended to be turned on if vppreproc is called with --Debug as an option.
However Verilog::Getopt::parameter is called to extract VCS-like parameters before the main call to GetOptions which parses parameters like --Debug. As a consequence debug messages associated with parsing VCS-like parameters can never be printed.
I found this when trying to debug a problem with the -f option.
vppreproc --debug -f foo.f is intended to print the message
"*parameter_file $filename\n", but does not do so.
Test case to follow shortly.
#1 Updated by Wilson Snyder almost 2 years ago
- Status changed from New to Resolved
- Assignee changed from Jeremy Bennett to Wilson Snyder
No need for a test, easy to recreate. Fixed in git towards 3.314(159 :).
However note that Verilog::Getopt's $Debug isn't the same as the script's $Debug, so fixing this alone won't get you that message. In vppreproc's "sub debug" you need to add "$Verilog::Getopt::Debug = 1;"