• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Functional Verification
  3. Can simvision tell me call-history of a (non-class based...

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 64
  • Views 711
  • 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

Can simvision tell me call-history of a (non-class based) Verilog-task/function?

cubicle82
cubicle82 over 16 years ago

I have a bunch of Verilog tasks (declared at module-scope.)  All of them call a common-function, let's say "utility_task();"

In debug (irun-08.20s008 -gui -linedebug -access +rwc ...), I put a breakpoint on utility_task().  This stops the simulator whenever utility_task() is called, but it won't tell me *WHO* called my task.  Is there a way to get simvision to give me the stack-history ofa Verilog task?

P.S. I know the 'stack' command works for Systemverilog class objects:

ncsim> stack
0: function autoevent.cls_a@1_1.function_a at ./autoevent.sv:30  // (silly recursive automatic function)
1: function autoevent.cls_a@1_1.function_b at ./autoevent.sv:19  // (silly recursive automatic function)
2: function autoevent.cls_a@1_1.function_a at ./autoevent.sv:28
3: function autoevent.cls_a@1_1.function_b at ./autoevent.sv:19
4: function autoevent.cls_a@1_1.function_a at ./autoevent.sv:28
5: process in autoevent.wait_on_bogus_event.t1 at ./autoevent.sv:57

...But when I tried it on my module-scoped task, it simply reports the source-file name and line# of the breakpoint.  I.e., it doesn't add any helpful information:

ncsim>

stack0: process in autoevent.wait_on_bogus_event.t2 at ./autoevent.sv:64

  • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information