Bart Posted June 15, 2011 Report Share Posted June 15, 2011 Anyone tried the new +UVM_CONFIG_DB_TRACE option in UVM1.1? Is it broken? I'm using set & get calls on uvm_config_db and adding the +UVM_CONFIG_DB_TRACE option does not generate any new output. Whereas using the +UVM_RESOURCE_DB_TRACE option reports get calls for every sodding property in my testbench, including default_sequence for every UVC in every run phase; recording_detail for every component; etc etc. Is this the expected behavior? Are there no filtering options? I'm resorting to the old check_config_usage() call, the output of which is significantly worse than in UVM1.0EA.. Config debugging seems to be going backwards in UVM1.0/1.1. Given some of my users like the regexp options in config sets, this is getting painful.. Anyone have any good options for config debug in UVM1.0/1 besides the above? Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.