• 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) error

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 65
  • Views 14368
  • 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) error

Kursi
Kursi over 15 years ago

Hi,

 I got the following stack trace error in the elaboration phase, on running a test case with Intelligen.

 *** Error: OS signal 11 (segmentation violation) received 

 The user view stack trace in the specman.elog file shows the following content:

 ***** User View stack trace:

( 0x0)  elaboration
( 0x1)  pre specman run
( 0x2)  specman

*** No user modules are compiled

But all the files that I have loaded have compiled properly.

Could anyone say what this error is all about and how to overcome it???

Regards,

Kursi

 

  • Cancel
  • StephenH
    StephenH over 15 years ago

    Hi Kursi.

    It sounds like there may be a bug in some of the e code that's being run.
    If you try to access a struct or unit that's null, then compiled Specman code will crash.
    This happens becasue the compiler optimises for performance and doesn't add null struct checks into the compiled code.

    Try either:

    1. Load your e code instead of compiling it, then type "break on error" before issuing the test command.

    2.  When compiling your ecode, add "-debug" to the sn_compile.sh command. This turns on the null struct checks, so gives you a useful message instead of a crash.

    Let us know if that solves the problem.
    For urgent support, you should always try http://support.cadence.com/ first, as often the system can offer a solution right away.

     

    • 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