Home > Community > Forums > Digital Implementation > NanoRoute CRASH, need help.....VERSION SOC-E 52 Update 5

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: *

 NanoRoute CRASH, need help.....VERSION SOC-E 52 Update 5 

Last post Tue, Jun 24 2008 6:03 AM by archive. 1 replies.
Started by archive 24 Jun 2008 06:03 AM. Topic has 1 replies and 2096 views
Page 1 of 1 (2 items)
Sort Posts:
  • Tue, Jun 24 2008 6:03 AM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,950
    NanoRoute CRASH, need help.....VERSION SOC-E 52 Update 5 Reply

    hi, all

    Following is an excerpt from the encounter log file, the nanoroute just made a STACK TRACE....

    #Total number of violations on LAYER M6 = 0
    #Total number of violations on LAYER M7 = 0
    #Total number of violations on LAYER M8 = 0
    #
    #Cpu time = 00:20:16
    #Elapsed time = 00:05:45
    #Increased memory = -34.00 (Mb)
    #Total memory = 3671.00 (Mb)
    #Peak memory = 4184.00 (Mb)
    **DIAG[dbRipin.c:1254:dbiInitRipinJncList]: Assert "dbmRipinFirstChild(ppp) == p"
    **DIAG[dbRipin.c:1254:dbiInitRipinJncList]: Assert "dbmRipinFirstChild(ppp) == p"
    Encounter terminated by internal (SEGV) error/signal...
    *** Stack trace:
    /data/XXXXXXX/tools/cadence/SOC52/tools/fe/bin/64bit/encounter(syStackTrace+0x127)[0x3c3f102]
    /data/XXXXXXX/tools/cadence/SOC52/tools/fe/bin/64bit/encounter[0xc1a3db]
    /lib64/libpthread.so.0[0x2a955963f8]
    /lib64/libc.so.6[0x2a95df9150]
    /data/XXXXXXX/tools/cadence/SOC52/tools/fe/bin/64bit/encounter(_Z26dbNetCleanupDuplicateRipinP6dbsNetc+0x10ea)[0x325be8e]
    /data/XXXXXXX/tools/cadence/SOC52/tools/fe/bin/64bit/encounter(_Z16dbNetRipinToWireP6dbsNet+0xa60)[0x325e578]
    /data/XXXXXXX/tools/cadence/SOC52/tools/fe/bin/64bit/encounter(_ZN11PDZT_Export12export_ripinEP14PDBT_Cell_ViewP8PDBT_Netb+0x1cd)[0xdf16bd]
    /data/XXXXXXX/tools/cadence/SOC52/tools/fe/bin/64bit/encounter(_ZN11PDZT_Export12export_ripinEv+0x8e)[0xdf149e]
    /data/XXXXXXX/tools/cadence/SOC52/tools/fe/bin/64bit/encounter(_ZN11PDZT_Export10export_netEv+0xd4)[0xdf0994]
    /data/XXXXXXX/tools/cadence/SOC52/tools/fe/bin/64bit/encounter(_ZN11PDZT_Export13export_designEv+0x21b)[0xdef64b]
    /data/XXXXXXX/tools/cadence/SOC52/tools/fe/bin/64bit/encounter(_ZN11PDZT_Export11auto_exportEv+0x7b)[0xdef27b]
    /data/XXXXXXX/tools/cadence/SOC52/tools/fe/bin/64bit/encounter(_ZN9PDIT_Main8call_cmdEiPPcb+0x331)[0xdf8861]
    /data/XXXXXXX/tools/cadence/SOC52/tools/fe/bin/64bit/encounter(TclInvokeStringCommand+0x7d)[0x44dd3a7]
    /data/XXXXXXX/tools/cadence/SOC52/tools/fe/bin/64bit/encounter(TclExecuteByteCode+0x89f)[0x44f7a04]

    As we know, encounter just calls nanoroute to route the design, and then ripin the routed database, I think the RED line is where the problems come from, need expert to give me a answer, I dont have access to sourcelink........

    BRs


    Originally posted in cdnusers.org by eminemshow
    • Post Points: 0
  • Tue, Jun 24 2008 7:20 AM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,950
    RE: NanoRoute CRASH, need help.....VERSION SOC-E 52 Update 5 Reply

    Would it be possible for you to work this issue through your local support contacts?

    Thanks,
    Bob


    Originally posted in cdnusers.org by BobD
    • Post Points: 0
Page 1 of 1 (2 items)
Sort Posts:
Started by archive at 24 Jun 2008 06:03 AM. Topic has 1 replies.