![[logo]](/img/veripool_small.png)
Issue #442
vppreproc --debug option does not enable debug messages for VCS-like parameters
| Status: | Closed | Start date: | 02/22/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | Wilson Snyder | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - |
Description
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.
History
Updated by Wilson Snyder about 1 year 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;"
Updated by Jeremy Bennett about 1 year ago
Thanks for the fix. I note that you left the assignment to $Verilog::Getopt::Debug = 1; commented out in vppreproc's sub debug. Was that deliberate?
Updated by Wilson Snyder about 1 year ago
Actually no, but now that it's there I'll probably leave it.
Also available in: Atom