• 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. How to solve the error:"Function xmdbg_fatal not define...

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 65
  • Views 2792
  • 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

How to solve the error:"Function xmdbg_fatal not define"

akdfkfjgh
akdfkfjgh over 2 years ago

hi

I run xmsim in a mixed environment( including verilog & c++ (using dpi to in import)), and the simulation is end with a error: SIGUSR

I read cadence document and try to use gdb to find the problem in c++ code.
However, when I follow the instruction shown below,  gdb return :function xmdbg_fatal not defined

  • Cancel
  • StephenH
    StephenH over 2 years ago

    Try setting the breakpoint on the function xmdbg_fatal as per the doc, you have a typo in your command as per your screenshot :)

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • akdfkfjgh
    akdfkfjgh over 2 years ago in reply to StephenH

    thx. I read newest docu and found thd function name has change from xmdbg_fatal to serror. Xmdbg_fatal is still not work.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • StephenH
    StephenH over 2 years ago in reply to akdfkfjgh

    Try ncdbg_fatal. It looks like someone inadvertently changed the doc from "nc" to "xm" when Incisive was renamed to Xcelium...

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • akdfkfjgh
    akdfkfjgh over 2 years ago in reply to StephenH

    thank you, ncdbg_fatal works!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • StephenH
    StephenH over 2 years ago in reply to StephenH

    Great, I'm glad it's resolved. FYI if you ever hit any problems with the docs, please use the "Feedback" button of the right side of the screen to alert the docs team to the problem. Try to make the explanation easy to understand because the team won't necessarily know the reason you think the docs are wrong. The team are very good and always respond quickly to fix issues when they get reported.

    For example, I just submitted this:

    • 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