• 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. While debugging systemverilog@incisive, how do I print ...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 65
  • Views 2739
  • 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

While debugging systemverilog@incisive, how do I print "this"?

Avidan
Avidan over 6 years ago

xcelium> run -step

../uvm-1.2/src/base/uvm_objection.svh:829       comp.raised(this, source_obj, description, count);

xcelium> value this

xmsim: *E,PNOOBJ: Path element could not be found: this.

Thanks,

Avidan

  • Cancel
Parents
  • StephenH
    StephenH over 6 years ago

    "this" is not a variable which is why the debugger won't print it. If you use the "where" command it will print the class handle of the scope you're in, which is the same thing as "this".

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • Avidan
    Avidan over 6 years ago in reply to StephenH

    Thanks. So say I'm stopped somewhere in a uvm_component, how do I print m_name? will this work?

    value [where].m_name

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Avidan
    Avidan over 6 years ago in reply to StephenH

    Thanks. So say I'm stopped somewhere in a uvm_component, how do I print m_name? will this work?

    value [where].m_name

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • StephenH
    StephenH over 6 years ago in reply to Avidan

    No, just "value m_name". Just like in SV, you do not need to prefix class variables with "this" unless you are trying to disambiguate between a class variable and a function's local variable.

    • Cancel
    • Vote Up 0 Vote Down
    • 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