• 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. Digital Implementation
  3. encounter SEGV internal error (with optDesign -postRoute...

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 92
  • Views 1508
  • 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

encounter SEGV internal error (with optDesign -postRoute)

MadapusiSriniv
MadapusiSriniv over 10 years ago

Hello *,

I am trying to debug an encounter SEGV internal error - termination issue with optDesign -postRoute (using the post Route engine-works fine with other engines)  I have attached part of the log at the end of this message.

I am not sure what is going wrong, this placed design works fine with other Tech files -when i load a different tech file into the saveDesign image and perform optDesign postRoute, and extract timing.

So I am concluding that it has something to do with the ICT/TECH file of the buggy run which might be triggering this issue . Please do advice me how to proceed with this.

LOGFILE:

Extraction called for design 'des' of instances=36916 and nets=38779 using extraction engine 'postRoute' at effort level 'high' .

**WARN: (ENCEXT-3530):  Use of command 'setDesignMode -process <process_node>' prior to extraction is recommended for maximum accuracy and optimal automatic threshold setting.

Integrated QRC (IQRC) Extraction called for design 'des'.

No IQRC parasitic data in encounter. Going for fullchip extraction.

Encounter terminated by internal (SEGV) error/signal...

*** Stack trace:

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter(syStackTrace+0x145)[0xf3b11fd]

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter[0x8f118d7]

[0xf7732410]

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter(_ZN11Cce_Session10InitializeEv+0x55d)[0x1110a79d]

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter(_Z16qxCCEGetHaloSizePcS_iPd+0x15c)[0xbc7ae9c]

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter[0xbc5ae84]

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter[0xbc5d93f]

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter[0xbc5f7bb]

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter(_Z14dcRCExtractionPc+0x551)[0xbdad891]

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter(_Z17peRCExtractionCmdPvP10Tcl_InterpiPPc+0x770)[0xbcd9540]

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter(_ZN10tcmBaseCmd7executeEP10Tcl_InterpiPPc+0xfd)[0x103ce78d]

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter(_ZN6tcmMgr9cmdParserEPvP10Tcl_InterpiPPc+0xae)[0x103c75ae]

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter(TclInvokeStringCommand+0x4f)[0x10a71e2f]

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter(TclEvalObjvInternal+0x126)[0x10a72e46]

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter[0x10a992ee]

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter(TclCompEvalObj+0xa3)[0x10a98853]

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter(Tcl_EvalObjEx+0x206)[0x10a74176]

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter(Tcl_RecordAndEvalObj+0xb4)[0x10aa6804]

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter(Tcl_RecordAndEval+0x4d)[0x10aa66cd]

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter(_Z17rdaEditCmdLineEndPc+0x298)[0x8e98598]

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter(_Z9elEndLinev+0x11b)[0xd2447bb]

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter(_Z21el_callback_read_charv+0x273)[0xd248b23]

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter[0x10ae2922]

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter(Tcl_ServiceEvent+0x99)[0x10ac02e9]

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter(Tcl_DoOneEvent+0x136)[0x10ac0686]

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter(Tcl_AppInit+0x39c)[0x8e96f5c]

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter(Tcl_Main+0x1f4)[0x10abb814]

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter(_Z7fe_mainiPPc+0x393)[0x8e96893]

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter(main+0x5f)[0x8e9691f]

/lib/libc.so.6(__libc_start_main+0xe6)[0x194d36]

/tools/cadence/edi101/tools.lnx86/fe/bin/32bit/encounter[0x8e96341]

  • Cancel
Parents
  • KJ1827
    KJ1827 over 7 years ago



    i am facing this same problem on place stage. please help me out divya if you know any solution.  


    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • KJ1827
    KJ1827 over 7 years ago



    i am facing this same problem on place stage. please help me out divya if you know any solution.  


    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Kari
    Kari over 7 years ago in reply to KJ1827

    If you are getting a stack trace, and don't have any obvious errors earlier in the run that you can fix (check your complete log file first), then you need to file a service request so R&D can take a look.

    • 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