Stats

  • Locked Locked
  • Replies 5
  • Subscribers 91
  • Views 1875
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

settings to not echo expanded command lines in log/log.cmd file

prathima

Hi,

Is there any setting to avoid echoing of expanded command lines in log/log.cmd file?

For example,

I  am calling a procedure which has the following command:

set names [dbGet [dbGet -regexp -u -p top.insts.cell.name ${ptrn}].name] 

The log file/ cmd.log file has the command " [dbGet -regexp -u -p top.insts.cell.name ${ptrn}]" completely expanded to:

dbGet {0x2abc53c960 0x2abc53c8c8........ 0x2abc53c798.name}

Because of this the logfiles are bulky and difficult to parse. Please let me know if there is any way to avoid this?

Thanks & Regards,

Prathima. 

Parents

  •  Hi Prathima, Have you seen the following solution article on how to disable the logging of commands?

     http://support.cadence.com/wps/mypoc/cos?uri=deeplinkmin:ViewSolution;solutionNumber=11645174

     I think this may provide what you need.

Reply

  •  Hi Prathima, Have you seen the following solution article on how to disable the logging of commands?

     http://support.cadence.com/wps/mypoc/cos?uri=deeplinkmin:ViewSolution;solutionNumber=11645174

     I think this may provide what you need.

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.