• 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. OS Signal 11 (segmentation violation)

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 64
  • Views 13360
  • 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

OS Signal 11 (segmentation violation)

archive
archive over 17 years ago

I would like to call a function in systemc from specman. I wrote the type convertor, defined method port, connect it to the function in systemc block. Compilation, elaboration are all done.
When I call the function through method port, I got the fatal error,

OS Signal 11 (segmentation violation)

Can anyone please tell me what could be the reason/reasons to cause this error? Thanks


Originally posted in cdnusers.org by twk1156
  • Cancel
Parents
  • archive
    archive over 17 years ago

    This is usually a problem with some pointer in C, either you're accessing a null pointer or some other mistake.
    Have you tried a very simple SystemC function called from Specman, just to test your linking?
    Try just a dumb "hello world" first...


    Originally posted in cdnusers.org by stephenh
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 17 years ago

    This is usually a problem with some pointer in C, either you're accessing a null pointer or some other mistake.
    Have you tried a very simple SystemC function called from Specman, just to test your linking?
    Try just a dumb "hello world" first...


    Originally posted in cdnusers.org by stephenh
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

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

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