Home > Community > Forums > Functional Verification > NC: INTERNAL EXCEPTION

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

 NC: INTERNAL EXCEPTION 

Last post Mon, Apr 7 2014 5:13 AM by StephenH. 1 replies.
Started by zxchit 21 Mar 2014 01:08 AM. Topic has 1 replies and 237 views
Page 1 of 1 (2 items)
Sort Posts:
  • Fri, Mar 21 2014 1:08 AM

    • zxchit
    • Not Ranked
    • Joined on Fri, Mar 21 2014
    • Posts 1
    • Points 20
    NC: INTERNAL EXCEPTION Reply

    I got following informaiton, who can tell me why? Thansks.

    By the way, I'm using a uvm enviroment.

     

    ncelab: *F,INTERR: INTERNAL EXCEPTION
    -----------------------------------------------------------------
    The tool has encountered an unexpected condition and must exit.
    Contact Cadence Design Systems customer support about this
    problem and provide enough information to help us reproduce it,
    including the logfile that contains this error message.
      TOOL: ncelab(64) 12.20-s012
      HOSTNAME: shalcs42
      OPERATING SYSTEM: Linux 2.6.18-274.el5 #1 SMP Fri Jul 8 17:36:59 EDT 2011 x86_64
      MESSAGE: xst_internal_error - default
    -----------------------------------------------------------------
    csi-ncelab - CSI: Cadence Support Investigation, sending details to /sdr/sdr_as/local_user/legsun/tb_pa587106_a1/sim/DMS/test/ncelab.err
    csi-ncelab - CSI: investigation complete, send /sdr/sdr_as/local_user/legsun/tb_pa587106_a1/sim/DMS/test/ncelab.err to Cadence Support
    irun: *E,ELBERR: Error during elaboration (status 255), exiting.
    TOOL: irun(64) 12.20-s012: Exiting on Mar 21, 2014 at 15:35:20 HKT  (total: 00:00:16)

    • Post Points: 20
  • Mon, Apr 7 2014 5:13 AM

    • StephenH
    • Top 25 Contributor
    • Joined on Tue, Sep 2 2008
    • Bristol, Avon
    • Posts 268
    • Points 4,310
    Re: NC: INTERNAL EXCEPTION Reply

     Hi zxchit.

    For this problem you'll need to go to http://support.cadence.com/ and file a support request, attaching the ncelar.err file and giving some more detail on the events leading up to the crash. This is quite a generic crash message with no specific root cause, so we'll need to dig into it in more depth.

     

    Steve Hobbs / Applications Engineer / Cadence Functional Verification
    • Post Points: 5
Page 1 of 1 (2 items)
Sort Posts:
Started by zxchit at 21 Mar 2014 01:08 AM. Topic has 1 replies.